search for: 0x486

...c/0x1e [<ffffffff81112e31>] irq_work_run+0x77/0x9b [<ffffffff810063e2>] smp_irq_work_interrupt+0x2a/0x31 [<ffffffff8158739d>] irq_work_interrupt+0x6d/0x80 [<ffffffff81585336>] ? _raw_spin_unlock_irqrestore+0x41/0x6a [<ffffffff810f5402>] rcu_process_callbacks+0x162/0x486 [<ffffffff810c4140>] ? run_timer_softirq+0x19f/0x1c0 [<ffffffff810be612>] __do_softirq+0xe1/0x1e9 [<ffffffff810be8b7>] irq_exit+0x40/0x87 [<ffffffff810283f1>] smp_apic_timer_interrupt+0x3f/0x4b [<ffffffff81586e9d>] apic_timer_interrupt+0x6d/0x80 <EOI> Code...

...n_write_failed+0xf7/0x14a [ 413.409157] [<ffffffff8120d7f3>] call_rwsem_down_write_failed+0x13/0x20 [ 413.409157] [<ffffffff8161d555>] ? down_write+0x2e/0x32 [ 413.409157] [<ffffffff81105701>] thaw_super+0x1f/0xa7 [ 413.409157] [<ffffffff8111217b>] do_vfs_ioctl+0x202/0x486 [ 413.409157] [<ffffffff81129733>] ? SyS_fstatfs+0x33/0x3f [ 413.409157] [<ffffffff8111245d>] SyS_ioctl+0x5e/0x85 [ 413.409157] [<ffffffff8161fdc6>] system_call_fastpath+0x1a/0x1f [ 413.409157] Sched Debug Version: v0.10, 3.10.0-rc5 #1 [ 413.409157] ktime...

Paolo Bonzini <pbonzini at redhat.com> wrote: > Il 29/05/2014 19:45, Chris Webb ha scritto: >> Chris Webb <chris at arachsys.com> wrote: >> >>> My CPU flags inside the crashing guest look like this: >>> >>> fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush >>> mmx fxsr sse sse2 ht syscall nx mmxext

Paolo Bonzini <pbonzini at redhat.com> wrote: > Il 29/05/2014 19:45, Chris Webb ha scritto: >> Chris Webb <chris at arachsys.com> wrote: >> >>> My CPU flags inside the crashing guest look like this: >>> >>> fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush >>> mmx fxsr sse sse2 ht syscall nx mmxext

...k lib/dump_stack.c:77 [inline] > dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113 > print_deadlock_bug kernel/locking/lockdep.c:1765 [inline] > check_deadlock kernel/locking/lockdep.c:1809 [inline] > validate_chain kernel/locking/lockdep.c:2405 [inline] > __lock_acquire.cold.65+0x1fb/0x486 kernel/locking/lockdep.c:3435 > lock_acquire+0x1e4/0x540 kernel/locking/lockdep.c:3924 > percpu_down_read_preempt_disable include/linux/percpu-rwsem.h:36 [inline] > percpu_down_read include/linux/percpu-rwsem.h:59 [inline] > cpus_read_lock+0x43/0xa0 kernel/cpu.c:289 > static_key...

...k lib/dump_stack.c:77 [inline] > dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113 > print_deadlock_bug kernel/locking/lockdep.c:1765 [inline] > check_deadlock kernel/locking/lockdep.c:1809 [inline] > validate_chain kernel/locking/lockdep.c:2405 [inline] > __lock_acquire.cold.65+0x1fb/0x486 kernel/locking/lockdep.c:3435 > lock_acquire+0x1e4/0x540 kernel/locking/lockdep.c:3924 > percpu_down_read_preempt_disable include/linux/percpu-rwsem.h:36 [inline] > percpu_down_read include/linux/percpu-rwsem.h:59 [inline] > cpus_read_lock+0x43/0xa0 kernel/cpu.c:289 > static_key...

...line] > > dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113 > > print_deadlock_bug kernel/locking/lockdep.c:1765 [inline] > > check_deadlock kernel/locking/lockdep.c:1809 [inline] > > validate_chain kernel/locking/lockdep.c:2405 [inline] > > __lock_acquire.cold.65+0x1fb/0x486 kernel/locking/lockdep.c:3435 > > lock_acquire+0x1e4/0x540 kernel/locking/lockdep.c:3924 > > percpu_down_read_preempt_disable include/linux/percpu-rwsem.h:36 [inline] > > percpu_down_read include/linux/percpu-rwsem.h:59 [inline] > > cpus_read_lock+0x43/0xa0 kernel/cpu.c:...

Hi, Chris (cc) and I try to get the SGE master monitor work with Apple Leopard dtrace. Unfortunately we are stuck with the error msg below. Anyone having an idea what could be the cause? What I can rule out as cause is function inlining for the reasons explained below. Background information on SGE master monitor implementation is under http://wiki.gridengine.info/wiki/index.php/Dtrace