search for: 0000000000000021

With lightweight desktoping, the atomic modesetting seems far from robust. BUG: unable to handle kernel NULL pointer dereference at 0000000000000021 IP: dma_fence_wait_timeout+0x36/0xf0 ... Oops: 0000 [#1] SMP Modules linked in: ... nouveau ... CPU: 0 PID: 6895 Comm: Xorg Not tainted 4.10.5-1001.fc24.x86_64 #1 ... Call Trace: drm_atomic_helper_wait_for_fences+0x48/0x120 [drm_kms_helper] nv50_disp_atomic_commit+0x19c/0x2a0 [nouveau] drm_atomi...

...ceeea1f8 (XEN)    000000d000000004 000000000000005a 00000000dd6a0000 aaaaaaaaaaaaaaaa (XEN)    aaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaa ffff8300ceeea000 ffff8300ceeea000 (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN)    00007cf6e65500c7 ffff82c480214ec1 00000000c0101427 0000000000000021 (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN)    00000000edab3ed4 000000000000000d 0000000000000000 0000000000000000 (XEN)    0000000000000000 0000000000000000 0000000000000021 000000000a0fa004 (XEN) Xen call trace: (XEN)    [<ffff82c480161a08>] pci_enable...

...[nouveau] [ 4036.404272] task: ffff8801fd3e5b00 ti: ffff88006e148000 task.ti: ffff88006e148000 [ 4036.404274] RIP: 0010:[<ffffffffc0241d95>] [<ffffffffc0241d95>] gk104_fifo_recover_work+0x95/0x280 [nouveau] [ 4036.404319] RSP: 0018:ffff88006e14bde0 EFLAGS: 00000206 [ 4036.404322] RAX: 0000000000000021 RBX: 0000000200000000 RCX: 0000000000000021 [ 4036.404324] RDX: 0000000000000001 RSI: 0000000000000282 RDI: 0000000000000282 [ 4036.404326] RBP: ffff88006e14be18 R08: ffff880098294b40 R09: 00000001802a001b [ 4036.404328] R10: 0000000098294d01 R11: 0000000000008000 R12: 0000000200000000 [ 4036.40433...

...rcoe at wi.rr.com QA Contact: xorg-team at lists.x.org Created attachment 130660 --> https://bugs.freedesktop.org/attachment.cgi?id=130660&action=edit kernel messages log Sorry if this is drm error and not a nouveau error. BUG: unable to handle kernel NULL pointer dereference at 0000000000000021 IP: dma_fence_wait_timeout+0x30/0x110 I had just started the computer, and started X with startx (because reasons). I had opened the configure prefences when the mouse froze. I'm including the kernel boot messages and traceback as an attachment. libdrm_nouveau2-32bit-2.4.75-1.1.x86_64 libdrm...

...00000000 0000000100000001 ffff82c48012411e (XEN) ffff82c4802b0880 00000000ffffffff ffff82c480297ef8 ffff82c480121fba (XEN) ffff82c48015854f ffff8300baff4000 0000000000000001 ffff88003dc07200 (XEN) 0000000000000001 ffffffff81996456 00007d3b7fd680c7 ffff82c4802056d8 (XEN) ffffffff8100142a 0000000000000021 ffffffff81996456 0000000000000001 (XEN) ffff88003dc07200 0000000000000001 ffffffff81a01da8 ffff88003dc07200 (XEN) 0000000000000246 ffff88003dc07200 0000000000000000 00000000a58856ce (XEN) 0000000000000021 ffffffff8100142a ffff88003dc05600 ffffffff81a01d88 (XEN) 0000000000000005 00000100...

...omain_crash_sync called from entry.S (XEN) Domain 0 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-4.2-unstable x86_64 debug=y Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e033:[<ffffffff81a8f18e>] (XEN) RFLAGS: 0000000000000206 EM: 1 CONTEXT: pv guest (XEN) rax: ffffffff81fd3000 rbx: 0000000000000021 rcx: 0000000000001000 (XEN) rdx: ffffffff81fd2000 rsi: 0000000000001000 rdi: 0000000000001000 (XEN) rbp: 0000000000000088 rsp: ffffffff81a01d38 r8: 0000000000000088 (XEN) r9: 0000000000000021 r10: 0000000000000000 r11: 0000000100000000 (XEN) r12: 0000000000079700 r13: 000000000000...

...000000000 DF *UND* 0000000000000077 Base _ZNKSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEE7compareEmmPKcm 0000000000000000 DF *UND* 0000000000000040 Base _ZNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEE6resizeEmc 0000000000000000 DF *UND* 0000000000000021 GCC_3.0 __deregister_frame 0000000000000000 DF *UND* 0000000000000005 Base _ZNSt3__118condition_variable10notify_allEv 0000000000000000 DF *UND* 00000000000000fa Base new_panel 0000000000000000 DF *UND* 0000000000000873 GLIBC_2.2.5 setlocale 0000000000000000...

...00000000 00000000da000000 aaaaaaaaaaaaaaaa (XEN) 0000000000000002 0000000000000025 00000000da000000 0000000000000000 (XEN) ffff83023ff2fed8 ffff8300bf4c8000 0000000000000011 ffff88002efa3a00 (XEN) 0000000000000011 00000000000000a0 00007cfdc00d00c7 ffff82c4801fb8e2 (XEN) ffffffff8100142a 0000000000000021 00000000000000a0 0000000000000011 (XEN) ffff88002efa3a00 0000000000000011 ffff88002db9d608 00000000000007c9 (XEN) 0000000000000217 0000000000000000 ffff88002bab02a0 ffff88002e45ac00 (XEN) 0000000000000021 ffffffff8100142a 0000000000000000 ffff88002db9d568 (XEN) Xen call trace: (XEN) [&l...

...174] FS: 00007f94d60dc7c0(0000) GS:ffff88001f400000(0000) knlGS:0000000000000000 [ 14.640174] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 14.640174] CR2: 0000000000000000 CR3: 000000001fad9000 CR4: 00000000000006f0 [ 14.640174] Stack: [ 14.640174] ffff88001faefd70 ffff88001e025280 0000000000000021 0000000000001000 [ 14.640174] ffff88001f9d5e00 ffffea000070ebc0 ffff88001faefe58 ffffffff8110a1ca [ 14.640174] ffff88001f9d5e10 ffff88001faefe90 ffff88001faefea0 0000000000000000 [ 14.640174] Call Trace: [ 14.640174] [<ffffffff8110a1ca>] generic_file_aio_read+0x2ca/0x700 [ 14.640...

Hello, I update my building scripts to build LLVM 4.0 RC1 (with clang, lldb, libc++, libc++abi, lld) on CentOS 6 and I got a lot of undefined symbols during linking LLDB. I'm using clang-3.9 and this configuration: -DLLVM_TARGETS_TO_BUILD="X86" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++

...000000000000000 CR3: 00000004168a9000 CR4: 00000000001407e0 [ 10.578073] Stack: [ 10.578074] ffffffffffffffe0 00000000ffffffed ffffffffa0750c30 ffff8804141cb950 [ 10.578075] ffffffffa0685322 ffff880416b84200 ffff88041768b000 0000000000000023 [ 10.578076] 000000000000002d ffff88041768b110 0000000000000021 ffff8804141cb9b8 [ 10.578076] Call Trace: [ 10.578099] [<ffffffffa0685322>] nouveau_object_ctor+0x68/0xa5 [nouveau] [ 10.578126] [<ffffffffa06c1f0c>] nouveau_devobj_ctor+0x521/0x5b4 [nouveau] [ 10.578146] [<ffffffffa06852e5>] nouveau_object_ctor+0x2b/0xa5 [nouveau] [...

...802e7f00 ffff82d0802c8000 ffffffff00000013 (XEN) 0000000000000002 ffff82d0802cfee0 ffff82d080128019 ffff82d0802c8000 (XEN) ffff82d0802c8000 ffff8300bcffc000 000000000000003e 4000000000000000 (XEN) 000000000000003e 0000000000000013 00007d2f7fd300c7 ffff82d0802248db (XEN) ffffffff8100142a 0000000000000021 ffffffff81c01fd8 ffffffff81c01fd8 (XEN) ffffffff81c01fd8 0000000000000000 ffff880427403ee0 ffff880404e82f00 (XEN) 0000000000000202 0000000000000015 ffff880410800000 ffff880404e82f00 (XEN) 0000000000000021 ffffffff8100142a 0000000000000000 ffff880427403ecc (XEN) 000000000000000c 00010100...

Hi, I''ve still have problems with ACPI(?) on Xen. After some system startup or resume CPU temperature goes high although all domUs (and dom0) are idle. On "good" system startup it is about 50-55C, on "bad" - above 67C (most time above 70C). I''ve noticed difference in C-states repored by Xen (attached files). On "bad" startups in addition suspend

Hi, i have big trouble with a Debian Lenny dom0 and latest kernel 2.6.32.19 with xen-4.0.1rc5. Due some reason the system freezes from time to time. I used kernel 2.6.31.9 with xen-3.4.2 before. The machine doesn''t write anything to serial console so there are no errors or something like that. Perhaps there is something to see from the logs ... Hardware Board: Intel DQ45CB CPU: