search for: 0xe1

...0 4142 4086 ffff88013147b998 0000000000000046 ffff88013147b938 ffffffff8025aea3 0000000000000000 ffff88013142acc0 ffff88007ffee340 ffff88013142b078 0000000100078e31 0000000000000246 0000000000000292 ffffffffa02b102b Call Trace: [<ffffffff8025aea3>] ? print_lock_contention_bug+0x1b/0xe1 [<ffffffffa02b102b>] ? dlm_put_lockspace+0x18/0x2b [dlm] [<ffffffff804e6cfd>] schedule+0x9/0x1d [<ffffffff804e702f>] schedule_timeout+0x28/0x176 [<ffffffff804e6dce>] ? wait_for_common+0x3d/0x11e [<ffffffff804e6e57>] wait_for_common+0xc6/0x11e [<ffffffff80232c8...

...a707000 ffff880028321168 000000000001b7ea 0000816be9b3faa2 Apr 22 09:11:49 daisy kernel: [142441.721130] Call Trace: Apr 22 09:11:49 daisy kernel: [142441.721139]? [<ffffffff8114f130>] ? sync_page+0x0/0x50 Apr 22 09:11:49 daisy kernel: [142441.721144]? [<ffffffff8107c851>] ? update_curr+0xe1/0x1f0 Apr 22 09:11:49 daisy kernel: [142441.721149]? [<ffffffff81566c55>] schedule_timeout+0x215/0x2f0 Apr 22 09:11:49 daisy kernel: [142441.721155]? [<ffffffff81067432>] ? check_preempt_curr+0x82/0xa0 Apr 22 09:11:49 daisy kernel: [142441.721159]? [<ffffffff815669b4>] wait_for_co...

You are right. But when i defined my instruction as follows: def P_256B_VADD : I<0xE1, MRMDestReg, (outs VRP_2048:$dst), (ins VRP_2048:$src1, VRPIM_2048:$src2),"P_256B_VADD\t{$src1, $src2, $dst|$dst, $src1, $src2}", [(set VRP_2048:$dst, (add (v64i32 VRP_2048:$src1), (v64i32 VRP_2048:$src2)))]>, VEX_4V; I get opcode conflicts? Then what to do? On Tue, Sep 5, 2017 at 3:...

...d4, 0xd5, 0xd7 }, { 0xd4, 0xd5, 0xd6, 0xd8 }, { 0xd5, 0xd6, 0xd7, 0xd9 }, { 0xd6, 0xd7, 0xd8, 0xda }, { 0xd7, 0xd8, 0xd9, 0xdb }, { 0xd8, 0xd9, 0xda, 0xdc }, { 0xd9, 0xda, 0xdb, 0xdd }, { 0xda, 0xdb, 0xdc, 0xde }, { 0xdb, 0xdc, 0xdd, 0xdf }, { 0xdc, 0xdd, 0xde, 0xe0 }, { 0xdd, 0xde, 0xdf, 0xe1 }, { 0xde, 0xdf, 0xe0, 0xe2 }, { 0xdf, 0xe0, 0xe1, 0xe3 }, { 0xe0, 0xe1, 0xe2, 0xe4 }, { 0xe1, 0xe2, 0xe3, 0xe5 }, { 0xe2, 0xe3, 0xe4, 0xe6 }, { 0xe3, 0xe4, 0xe5, 0xe7 }, { 0xe4, 0xe5, 0xe6, 0xe8 }, { 0xe5, 0xe6, 0xe7, 0xe9 }, { 0xe6, 0xe7, 0xe8, 0xea }, { 0xe7, 0xe8, 0xe9, 0xeb }, { 0xe...

...Topper <craig.topper at gmail.com> wrote: > Leave TA. Put both. > > ~Craig > > On Mon, Sep 4, 2017 at 4:00 PM, hameeza ahmed <hahmed2305 at gmail.com> > wrote: > >> You are right. But when i defined my instruction as follows: >> def P_256B_VADD : I<0xE1, MRMDestReg, (outs VRP_2048:$dst), (ins >> VRP_2048:$src1, VRPIM_2048:$src2),"P_256B_VADD\t{$src1, $src2, >> $dst|$dst, $src1, $src2}", [(set VRP_2048:$dst, (add (v64i32 >> VRP_2048:$src1), (v64i32 VRP_2048:$src2)))]>, VEX_4V; >> >> I get opcode conflicts?...

...000000000001b7ea 0000816be9b3faa2 > Apr 22 09:11:49 daisy kernel: [142441.721130] Call Trace: > Apr 22 09:11:49 daisy kernel: [142441.721139]? [<ffffffff8114f130>] ? > sync_page+0x0/0x50 > Apr 22 09:11:49 daisy kernel: [142441.721144]? [<ffffffff8107c851>] ? > update_curr+0xe1/0x1f0 > Apr 22 09:11:49 daisy kernel: [142441.721149]? [<ffffffff81566c55>] > schedule_timeout+0x215/0x2f0 > Apr 22 09:11:49 daisy kernel: [142441.721155]? [<ffffffff81067432>] ? > check_preempt_curr+0x82/0xa0 > Apr 22 09:11:49 daisy kernel: [142441.721159]? [<ffffffff...

...0816be9b3faa2 >> Apr 22 09:11:49 daisy kernel: [142441.721130] Call Trace: >> Apr 22 09:11:49 daisy kernel: [142441.721139]? [<ffffffff8114f130>] ? >> sync_page+0x0/0x50 >> Apr 22 09:11:49 daisy kernel: [142441.721144]? [<ffffffff8107c851>] ? >> update_curr+0xe1/0x1f0 >> Apr 22 09:11:49 daisy kernel: [142441.721149]? [<ffffffff81566c55>] >> schedule_timeout+0x215/0x2f0 >> Apr 22 09:11:49 daisy kernel: [142441.721155]? [<ffffffff81067432>] ? >> check_preempt_curr+0x82/0xa0 >> Apr 22 09:11:49 daisy kernel: [142441.72...

...d4, 0xd5, 0xd7 }, { 0xd4, 0xd5, 0xd6, 0xd8 }, { 0xd5, 0xd6, 0xd7, 0xd9 }, { 0xd6, 0xd7, 0xd8, 0xda }, { 0xd7, 0xd8, 0xd9, 0xdb }, { 0xd8, 0xd9, 0xda, 0xdc }, { 0xd9, 0xda, 0xdb, 0xdd }, { 0xda, 0xdb, 0xdc, 0xde }, { 0xdb, 0xdc, 0xdd, 0xdf }, { 0xdc, 0xdd, 0xde, 0xe0 }, { 0xdd, 0xde, 0xdf, 0xe1 }, { 0xde, 0xdf, 0xe0, 0xe2 }, { 0xdf, 0xe0, 0xe1, 0xe3 }, { 0xe0, 0xe1, 0xe2, 0xe4 }, { 0xe1, 0xe2, 0xe3, 0xe5 }, { 0xe2, 0xe3, 0xe4, 0xe6 }, { 0xe3, 0xe4, 0xe5, 0xe7 }, { 0xe4, 0xe5, 0xe6, 0xe8 }, { 0xe5, 0xe6, 0xe7, 0xe9 }, { 0xe6, 0xe7, 0xe8, 0xea }, { 0xe7, 0xe8, 0xe9, 0xeb }, { 0xe...

I''ve recently re-installed an X4500 running Nevada b109 and have been experiencing ZFS lock ups regularly (perhaps once every 2-3 days). The machine is a backup server and receives hourly ZFS snapshots from another thumper - as such, the amount of zfs activity tends to be reasonably high. After about 48 - 72 hours, the file system seems to lock up and I''m unable to do anything

...6_output+0x51/0x1b0 [<ffffffff815b51af>] mld_sendpack+0x19f/0x360 [<ffffffff815b59b4>] mld_ifc_timer_expire+0x194/0x290 [<ffffffff8104b794>] call_timer_fn+0x74/0xf0 [<ffffffff8104bb1b>] run_timer_softirq+0x18b/0x220 [<ffffffff81045f81>] __do_softirq+0xe1/0x1c0 [<ffffffff8160a4fc>] call_softirq+0x1c/0x30 Seems the function vring_add_indirect stores an array of struct vring_desc by using virt_to_phys and kmemleak doesn't track the pointer. The following patch can fix this. Signed-off-by: Alexandru Copot <alex.mihai.c at gmail.com&...

...6_output+0x51/0x1b0 [<ffffffff815b51af>] mld_sendpack+0x19f/0x360 [<ffffffff815b59b4>] mld_ifc_timer_expire+0x194/0x290 [<ffffffff8104b794>] call_timer_fn+0x74/0xf0 [<ffffffff8104bb1b>] run_timer_softirq+0x18b/0x220 [<ffffffff81045f81>] __do_softirq+0xe1/0x1c0 [<ffffffff8160a4fc>] call_softirq+0x1c/0x30 Seems the function vring_add_indirect stores an array of struct vring_desc by using virt_to_phys and kmemleak doesn't track the pointer. The following patch can fix this. Signed-off-by: Alexandru Copot <alex.mihai.c at gmail.com&...

...Put both. >>> >>> ~Craig >>> >>> On Mon, Sep 4, 2017 at 4:00 PM, hameeza ahmed <hahmed2305 at gmail.com> >>> wrote: >>> >>>> You are right. But when i defined my instruction as follows: >>>> def P_256B_VADD : I<0xE1, MRMDestReg, (outs VRP_2048:$dst), (ins >>>> VRP_2048:$src1, VRPIM_2048:$src2),"P_256B_VADD\t{$src1, $src2, >>>> $dst|$dst, $src1, $src2}", [(set VRP_2048:$dst, (add (v64i32 >>>> VRP_2048:$src1), (v64i32 VRP_2048:$src2)))]>, VEX_4V; >>>>...

...[24183.985513] Pid: 2605, comm: > > debootstrap Not tainted 3.0.0-1-amd64 #1 Intel Corporation > > S1200BTL/S1200BTL > > Sep 10 22:35:33 xen-dom0 kernel: [24183.985621] RIP: > > e030:[<ffffffff810106db>] [<ffffffff810106db>] > > __sanitize_i387_state+0x23/0xe1 > > Source/disassembly: > > void __sanitize_i387_state(struct task_struct *tsk) > { > u64 xstate_bv; > int feature_bit = 0x2; > struct i387_fxsave_struct *fx = &tsk->thread.fpu.state->fxsave; > ffffffff810106b8: 48 8b 97 48 04 00 00 mov 0x448(%r...

...t;> Apr 22 09:11:49 daisy kernel: [142441.721130] Call Trace: >>> Apr 22 09:11:49 daisy kernel: [142441.721139]? [<ffffffff8114f130>] ? >>> sync_page+0x0/0x50 >>> Apr 22 09:11:49 daisy kernel: [142441.721144]? [<ffffffff8107c851>] ? >>> update_curr+0xe1/0x1f0 >>> Apr 22 09:11:49 daisy kernel: [142441.721149]? [<ffffffff81566c55>] >>> schedule_timeout+0x215/0x2f0 >>> Apr 22 09:11:49 daisy kernel: [142441.721155]? [<ffffffff81067432>] ? >>> check_preempt_curr+0x82/0xa0 >>> Apr 22 09:11:49 dais...

...ent allocation failed for device 0000:01:00.0 size=2097152 [ +0.000004] CPU: 6 PID: 1023 Comm: Xorg Not tainted 4.15.0-rc8 #1 [ +0.000003] Hardware name: Micro-Star International Co., Ltd. GX780/GT780/MS-1761, BIOS E1761IMS V3.01 05/02/2011 [ +0.000003] Call Trace: [ +0.000009] dump_stack+0x9f/0xe1 [ +0.000008] swiotlb_alloc_coherent+0xdf/0x150 [ +0.000010] ttm_dma_pool_get_pages+0x1ec/0x4b0 [ +0.000015] ttm_dma_populate+0x24c/0x340 [ +0.000011] ttm_tt_bind+0x23/0x50 [ +0.000006] ttm_bo_handle_move_mem+0x58c/0x5c0 [ +0.000015] ttm_bo_validate+0x152/0x190 [ +0.000004] ? ttm_bo_in...

...>>>> >>>>> On Mon, Sep 4, 2017 at 4:00 PM, hameeza ahmed <hahmed2305 at gmail.com> >>>>> wrote: >>>>> >>>>>> You are right. But when i defined my instruction as follows: >>>>>> def P_256B_VADD : I<0xE1, MRMDestReg, (outs VRP_2048:$dst), (ins >>>>>> VRP_2048:$src1, VRPIM_2048:$src2),"P_256B_VADD\t{$src1, $src2, >>>>>> $dst|$dst, $src1, $src2}", [(set VRP_2048:$dst, (add (v64i32 >>>>>> VRP_2048:$src1), (v64i32 VRP_2048:$src2)))]>, V...

Thank You. My add instruction has TA as follows: def P_256B_VADD : I<0xE1, MRMDestReg, (outs VRP_2048:$dst), (ins VRP_2048:$src1, VRPIM_2048:$src2),"P_256B_VADD\t{$src1, $src2, $dst|$dst, $src1, $src2}", [(set VRP_2048:$dst, (add (v64i32 VRP_2048:$src1), (v64i32 VRP_2048:$src2)))]>, TA; so i defined; bool HasTA = TSFlags & X86II::TA; in x86MCCodeEmit...

Dear list, I read in ?plotmath that I can use bgroup to draw scalable delimiters such as [ ] and ( ). The same technique fails with < > however, and I cannot find a workaround, grid.text(expression(bgroup("<",atop(x,y),">"))) Error in bgroup("<", atop(x, y), ">") : invalid group delimiter Regards, baptiste sessionInfo() R version

Dear list, I read in ?plotmath that I can use bgroup to draw scalable delimiters such as [ ] and ( ). The same technique fails with < > however, and I cannot find a workaround, grid.text(expression(bgroup("<",atop(x,y),">"))) Error in bgroup("<", atop(x, y), ">") : invalid group delimiter Regards, baptiste sessionInfo() R version

...;> On Mon, Sep 4, 2017 at 4:00 PM, hameeza ahmed <hahmed2305 at gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>>> You are right. But when i defined my instruction as follows: >>>>>>>> def P_256B_VADD : I<0xE1, MRMDestReg, (outs VRP_2048:$dst), (ins >>>>>>>> VRP_2048:$src1, VRPIM_2048:$src2),"P_256B_VADD\t{$src1, $src2, >>>>>>>> $dst|$dst, $src1, $src2}", [(set VRP_2048:$dst, (add (v64i32 >>>>>>>> VRP_2048:$src1), (v64i32 V...