Hi Jesse,
I have another backtrace,but I can not sure the reason of rebooting.
This backtrace is similar to previous one, but I do not see the repeating
of same frames.
Is this backtrace still telling that loops led to rebooting?
Many thanks.
Faithfulman.
PID: 2101 TASK: ffff880930e74ae0 CPU: 14 COMMAND: "ovs-vswitchd"
#0 [ffff8800283039a0] machine_kexec at ffffffff81031f7b
#1 [ffff880028303a00] crash_kexec at ffffffff810b8c22
#2 [ffff880028303ad0] oops_end at ffffffff814ed6b0
#3 [ffff880028303b00] no_context at ffffffff81042a0b
#4 [ffff880028303b50] __bad_area_nosemaphore at ffffffff81042c95
#5 [ffff880028303ba0] bad_area_nosemaphore at ffffffff81042d63
#6 [ffff880028303bb0] __do_page_fault at ffffffff810434c1
#7 [ffff880028303cd0] do_page_fault at ffffffff814ef68e
#8 [ffff880028303d00] page_fault at ffffffff814eca45
[exception RIP: update_curr+324]
RIP: ffffffff81053264 RSP: ffff880028303db8 RFLAGS: 00010086
RAX: ffff880930e74ae0 RBX: 0000000030c0c0b8 RCX: ffff8804bfeed1c0
RDX: 0000000000019250 RSI: 0000000000000000 RDI: ffff880930e74b18
RBP: ffff880028303de8 R8: ffffffff8160b7e5 R9: 0000000000000002
R10: 0000000000000010 R11: 0000000000000002 R12: ffff8800283166e8
R13: 0000000000040f2a R14: 000001654558b177 R15: ffff880930e74ae0
ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018
#9 [ffff880028303df0] task_tick_fair at ffffffff8105381b
#10 [ffff880028303e20] scheduler_tick at ffffffff810570e1
#11 [ffff880028303e60] update_process_times at ffffffff8107cc8e
#12 [ffff880028303e90] tick_sched_timer at ffffffff810a0976
#13 [ffff880028303ec0] __run_hrtimer at ffffffff8109510e
#14 [ffff880028303f10] hrtimer_interrupt at ffffffff810954b6
#15 [ffff880028303f90] smp_apic_timer_interrupt at ffffffff814f1f9b
#16 [ffff880028303fb0] apic_timer_interrupt at ffffffff8100bb93
--- <IRQ stack> ---
bt: cannot transition from IRQ stack to current process stack:
IRQ stack pointer: ffff8800283039a0
process stack pointer: ffff880930c0bdc8
current stack base: ffff880930c0c000
crash>
2013/3/12 Jesse Gross <je...@nicira.com>
> On Mon, Mar 11, 2013 at 5:21 PM, 謝秉融 <faithful...@gmail.com> wrote:
> > Hi Jesse,
> > Can i know which part or lines of this stack trace indicating a loop?
>
> The fact that the same frames repeat over and over again.
>
> > If there is a loop,the kernel "must" crash and reboot?
> > Why do not ovs just block the path?
>
> There is no fully generic way to do that in this context.
>
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
