search for: 0x110

...: [ 1532.887246] [btrfs:btrfs_commit_transaction+0x3c8/0x700] :btrfs:btrfs_commit_transaction+0x3c8/0x700 Jul 24 22:44:54 minerva kernel: [ 1532.887314] [<ffffffff80253a00>] autoremove_wake_function+0x0/0x30 Jul 24 22:44:54 minerva kernel: [ 1532.887398] [btrfs:btrfs_transaction_cleaner+0xf0/0x110] :btrfs:btrfs_transaction_cleaner+0xf0/0x110 Jul 24 22:44:54 minerva kernel: [ 1532.887479] [btrfs:btrfs_transaction_cleaner+0x0/0x110] :btrfs:btrfs_transaction_cleaner+0x0/0x110 Jul 24 22:44:54 minerva kernel: [ 1532.887543] [run_workqueue+0xcc/0x170] run_workqueue+0xcc/0x170 Jul 24 22:44:54 miner...

Hello, I am using wine on RH9. I am running Visual Source Safe like thus wine --ssexp.exe THe VSS GUI starts OK. the Visual Source Safe database is on Windows Partition. This Windows Partition is mounted on my Linux like thus: mount -t nfs -o rw,nolock 192.168.0.77:/mnt/server/Share /mnt/vss I am able to launch a VSS session : I can successfully check out and check in files (I point my

...2:28 2013] Call Trace: [Fri Oct 18 10:52:28 2013] [<ffffffffa02969fb>] ? ocfs2_read_inode_block_full+0x3b/0x60 [ocfs2] [Fri Oct 18 10:52:28 2013] [<ffffffffa028b2be>] ocfs2_get_clusters+0x23e/0x3b0 [ocfs2] [Fri Oct 18 10:52:28 2013] [<ffffffff8109a9ad>] ? sched_clock_cpu+0xbd/0x110 [Fri Oct 18 10:52:28 2013] [<ffffffffa028b48a>] ocfs2_extent_map_get_blocks+0x5a/0x190 [ocfs2] [Fri Oct 18 10:52:28 2013] [<ffffffffa026eb3a>] ocfs2_direct_IO_get_blocks+0x5a/0x160 [ocfs2] [Fri Oct 18 10:52:28 2013] [<ffffffff811c87c1>] ? inode_dio_done+0x31/0x40 [Fri Oct 18...

...] ttm_bo_init_reserved+0x290/0x490 [ttm] [ 1313.811114] ttm_bo_init+0x52/0xb0 [ttm] [ 1313.811141] ? nv10_bo_put_tile_region+0x60/0x60 [nouveau] [ 1313.811163] nouveau_bo_new+0x465/0x5e0 [nouveau] [ 1313.811184] ? nv10_bo_put_tile_region+0x60/0x60 [nouveau] [ 1313.811203] nouveau_gem_new+0x66/0x110 [nouveau] [ 1313.811223] ? nouveau_gem_new+0x110/0x110 [nouveau] [ 1313.811241] nouveau_gem_ioctl_new+0x48/0xc0 [nouveau] [ 1313.811249] drm_ioctl_kernel+0x64/0xb0 [drm] [ 1313.811257] drm_ioctl+0x2a4/0x360 [drm] [ 1313.811276] ? nouveau_gem_new+0x110/0x110 [nouveau] [ 1313.811285] ? drm_ioct...

Hi all, I am trying to use the 0x110 SERIALIZE (or 0x108 WAIT_FOR_IDLE?) command to barrier the PGRAPH commands. Unfortunately, I do not find any examples either in nouveau or gallium. If it plays just a barrier, I guess it should work by something like (in case of m2mf): BEGIN_RING(chan, m2mf, 0x110, 1); OUT_RING(chan, 1); Otherwis...

...d/wine1.3-1.3.11/dlls/user32/message.c:3165] in user32 (0x0032f234) 13 0x715b3b4f in comctl32 (+0x23b4e) (0x0032f298) 14 0x7e9c63aa WINPROC_wrapper+0x19() in user32 (0x0032f2c8) 15 0x7e9c63aa WINPROC_wrapper+0x19() in user32 (0x0032f328) 16 0x7e9c7bfd call_dialog_proc+0x5c(hwnd=0x60398, msg=0x110, wp=0xb0396, lp=0x12c0a8, result=0x32f35c, arg=0x715b233b) [/build/buildd/wine1.3-1.3.11/dlls/user32/winproc.c:263] in user32 (0x0032f378) 17 0x7e9c7e3d WINPROC_CallDlgProcW+0x12c(func=0xffff001a, hwnd=0x60398, msg=0x110, wParam=0xb0396, lParam=0x715f402c) [/build/buildd/wine1.3-1.3.11/dlls/user3...

...r.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/nv_driver.c b/src/nv_driver.c index e726292..4c40763 100644 --- a/src/nv_driver.c +++ b/src/nv_driver.c @@ -377,6 +377,7 @@ NVHasKMS(struct pci_device *pci_dev, struct xf86_platform_device *platform_dev) case 0xf0: case 0x100: case 0x110: + case 0x120: break; default: xf86DrvMsg(-1, X_ERROR, "Unknown chipset: NV%02x\n", chipset); @@ -930,6 +931,7 @@ NVPreInit(ScrnInfoPtr pScrn, int flags) pNv->Architecture = NV_KEPLER; break; case 0x110: + case 0x120: pNv->Architecture = NV_MAXWELL; break; de...

...970817] [<ffffffff811c0717>] ? vmap_page_range_noflush+0x257/0x350 > [ 1.970823] [<ffffffff811c083e>] ? map_vm_area+0x2e/0x40 > [ 1.970829] [<ffffffff811c1590>] ? __vmalloc_node_range+0x170/0x270 > [ 1.970838] [<ffffffff81101249>] ? SyS_init_module+0x99/0x110 > [ 1.970846] [<ffffffff81101275>] SyS_init_module+0xc5/0x110 > [ 1.970856] [<ffffffff816b4fc9>] system_call_fastpath+0x16/0x1b > [ 1.970862] ---[ end trace 2117480876ed90d2 ]--- > [ 1.970869] vmalloc: allocation failure, allocated 24576 of 28672 bytes > [...

...>] nvkm_fb_init+0x27/0xe0 [nouveau] [<00000000fae7fedc>] nvkm_subdev_init+0xbc/0x210 [nouveau] [<00000000a67b86e4>] nvkm_device_init+0x12a/0x280 [nouveau] [<00000000c02ac03e>] nvkm_udevice_init+0x48/0x60 [nouveau] [<0000000048f35641>] nvkm_object_init+0x43/0x110 [nouveau] [<00000000c6f92dc0>] nvkm_object_init+0x74/0x110 [nouveau] [<00000000c6f92dc0>] nvkm_object_init+0x74/0x110 [nouveau] [<000000007416951c>] nvkm_client_resume+0xe/0x10 [nouveau] [<00000000c5d31dfd>] nvif_client_resume+0x1d/0x20 [nouveau] [<000...

...x290/0x490 [ttm] > [ 1313.811114] ttm_bo_init+0x52/0xb0 [ttm] > [ 1313.811141] ? nv10_bo_put_tile_region+0x60/0x60 [nouveau] > [ 1313.811163] nouveau_bo_new+0x465/0x5e0 [nouveau] > [ 1313.811184] ? nv10_bo_put_tile_region+0x60/0x60 [nouveau] > [ 1313.811203] nouveau_gem_new+0x66/0x110 [nouveau] > [ 1313.811223] ? nouveau_gem_new+0x110/0x110 [nouveau] > [ 1313.811241] nouveau_gem_ioctl_new+0x48/0xc0 [nouveau] > [ 1313.811249] drm_ioctl_kernel+0x64/0xb0 [drm] > [ 1313.811257] drm_ioctl+0x2a4/0x360 [drm] > [ 1313.811276] ? nouveau_gem_new+0x110/0x110 [nouveau] &...

...uot;zpool detech disk c6t7d0" to detech a mirror causes zpool command to hang with following kernel stack trace: PC: _resume_from_idle+0xf8 CMD: zpool detach disk1 c6t7d0 stack pointer for thread fffffe84d34b4920: fffffe8001c30c10 [ fffffe8001c30c10 _resume_from_idle+0xf8() ] swtch+0x110() cv_wait+0x68() spa_config_enter+0x50() spa_vdev_enter+0x2a() spa_vdev_detach+0x39() zfs_ioc_vdev_detach+0x48() zfsdev_ioctl+0x13e() cdev_ioctl+0x1d() spec_ioctl+0x50() fop_ioctl+0x25() ioctl+0xac() sys_syscall32+0x101() Other zpool commands, df, forma...

...1c0717>] ? vmap_page_range_noflush+0x257/0x350 >>> [ 1.970823] [<ffffffff811c083e>] ? map_vm_area+0x2e/0x40 >>> [ 1.970829] [<ffffffff811c1590>] ? __vmalloc_node_range+0x170/0x270 >>> [ 1.970838] [<ffffffff81101249>] ? SyS_init_module+0x99/0x110 >>> [ 1.970846] [<ffffffff81101275>] SyS_init_module+0xc5/0x110 >>> [ 1.970856] [<ffffffff816b4fc9>] system_call_fastpath+0x16/0x1b >>> [ 1.970862] ---[ end trace 2117480876ed90d2 ]--- >>> [ 1.970869] vmalloc: allocation failure, allocat...

...es the queue length. I'll try to figure out what's happening, but if it's obvious to someone else from the stack, please let me know. [ 72.322236] BUG: unable to handle kernel NULL pointer dereference at 0000000000000010 [ 72.329993] IP: [<ffffffff8153c1a0>] tun_device_event+0x110/0x340 [ 72.336032] PGD 7f054f1067 PUD 7ef6f3f067 PMD 0 [ 72.340616] Oops: 0002 [#1] SMP DEBUG_PAGEALLOC [ 72.345498] gsmi: Log Shutdown Reason 0x03 [ 72.349541] Modules linked in: w1_therm wire cdc_acm ehci_pci ehci_hcd mlx4_en ib_uverbs mlx4_ib ib_core mlx4_core [ 72.359870] CPU: 12 PID:...

...6253.341580] ttm_dma_populate+0x250/0x310 [ttm] [ 6253.341586] ttm_tt_populate+0x28/0x70 [ttm] [ 6253.341591] ttm_tt_bind+0x26/0x60 [ttm] [ 6253.341596] ttm_bo_handle_move_mem+0x51a/0x580 [ttm] [ 6253.341612] ? drm_mm_insert_node_in_range+0x42b/0x480 [drm] [ 6253.341617] ttm_bo_validate+0xfa/0x110 [ttm] [ 6253.341622] ? _raw_write_unlock+0x12/0x30 [ 6253.341634] ? drm_vma_offset_add+0x5c/0x70 [drm] [ 6253.341638] ttm_bo_init_reserved+0x296/0x450 [ttm] [ 6253.341643] ttm_bo_init+0x73/0xd0 [ttm] [ 6253.341675] ? nv10_bo_put_tile_region+0x50/0x50 [nouveau] [ 6253.341704] nouveau_bo_new+0x...

...es the queue length. I'll try to figure out what's happening, but if it's obvious to someone else from the stack, please let me know. [ 72.322236] BUG: unable to handle kernel NULL pointer dereference at 0000000000000010 [ 72.329993] IP: [<ffffffff8153c1a0>] tun_device_event+0x110/0x340 [ 72.336032] PGD 7f054f1067 PUD 7ef6f3f067 PMD 0 [ 72.340616] Oops: 0002 [#1] SMP DEBUG_PAGEALLOC [ 72.345498] gsmi: Log Shutdown Reason 0x03 [ 72.349541] Modules linked in: w1_therm wire cdc_acm ehci_pci ehci_hcd mlx4_en ib_uverbs mlx4_ib ib_core mlx4_core [ 72.359870] CPU: 12 PID:...

...0x80 [<ffffffff812c6d84>] register_con_driver+0x34/0x140 [<ffffffff812c84e9>] take_over_console+0x29/0x60 [<ffffffff8126e76b>] fbcon_takeover+0x5b/0xb0 [<ffffffff81272bb5>] fbcon_event_notify+0x715/0x820 [<ffffffff810693a5>] notifier_call_chain+0x55/0x110 [<ffffffff810697d7>] __blocking_notifier_call_chain+0x67/0xc0 [<ffffffff81069841>] blocking_notifier_call_chain+0x11/0x20 [<ffffffff81262a16>] fb_notifier_call_chain+0x16/0x20 [<ffffffff81264c1d>] register_framebuffer+0x1bd/0x2f0 [<ffffffff81ac2bd4>...

A recently created and fully functional CentOS 7.3 VM fails to boot after applying CR updates: ... ;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f

.../0x29e0 [ 1.970817] [<ffffffff811c0717>] ? vmap_page_range_noflush+0x257/0x350 [ 1.970823] [<ffffffff811c083e>] ? map_vm_area+0x2e/0x40 [ 1.970829] [<ffffffff811c1590>] ? __vmalloc_node_range+0x170/0x270 [ 1.970838] [<ffffffff81101249>] ? SyS_init_module+0x99/0x110 [ 1.970846] [<ffffffff81101275>] SyS_init_module+0xc5/0x110 [ 1.970856] [<ffffffff816b4fc9>] system_call_fastpath+0x16/0x1b [ 1.970862] ---[ end trace 2117480876ed90d2 ]--- [ 1.970869] vmalloc: allocation failure, allocated 24576 of 28672 bytes [ 1.970874] systemd-udevd...

...tl_setparam+0x10/0x10 [<ffffffff81a85ccb>] drm_ioctl+0x20b/0x6b0 [<ffffffff811bfc66>] ? debug_lockdep_rcu_enabled+0x26/0x40 [<ffffffff81a85ac0>] ? drm_ioctl_permit+0x120/0x120 [<ffffffff8118e23d>] ? trace_hardirqs_on+0xd/0x10 [<ffffffff81fe9f99>] nouveau_drm_ioctl+0x99/0x110 [<ffffffff813342be>] do_vfs_ioctl+0x4ae/0x800 [<ffffffff8180a3d9>] ? selinux_file_ioctl+0x1f9/0x2d0 [<ffffffff81333e10>] ? ioctl_preallocate+0x140/0x140 [<ffffffff8180a1e0>] ? selinux_parse_skb.constprop.42+0x7c0/0x7c0 [<ffffffff811dbdcb>] ? do_setitimer+0x28b/0x420 [&...

...s trying to acquire lock: [ 98.409442] ffff888753e39a80 (&vmm->mutex#3){+.+.}, at: nvkm_uvmm_mthd+0x4d5/0xbe0 [nouveau] [ 98.418064] [ 98.418064] but task is already holding lock: [ 98.423915] ffff888759cdc9b0 (&svmm->mutex){+.+.}, at: nouveau_svmm_invalidate_range_start+0x71/0x110 [nouveau] [ 98.434142] [ 98.434142] which lock already depends on the new lock. [ 98.434142] [ 98.442408] [ 98.442408] the existing dependency chain (in reverse order) is: [ 98.449899] [ 98.449899] -> #3 (&svmm->mutex){+.+.}: [ 98.455249] __mutex_lock+0x134/0xc7...