search for: show_trac

Hi Guys, Thanks for the interest in the xen hypervisor debugger, prev known as kdb. Btw. I''m gonna rename it to xdb for xen-debugger or hdb for hypervisor debugger. KDB is confusing people with linux kdb debugger and I often get emails where people think they need to apply linux kdb patch also... Anyways, attaching patch that is cleaned up of my debug code that I accidentally left in

...: fpu tsc msr pae mce cx8 mtrr mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow up ts bogomips : 9928.70 ? Also I am receiving a kernel-bug message When I try to create a domU BUG: warning at kernel/lockdep.c:1814/trace_hardirqs_on() (Not tainted) [<c040566e>] show_trace_log_lvl+0x58/0x177 [<c0405c73>] show_trace+0xd/0x10 [<c0405cb1>] dump_stack+0x19/0x1b [<c043646e>] trace_hardirqs_on+0xa4/0x120 [<c0404e67>] restore_all+0x37/0x3a DWARF2 unwinder stuck at restore_all+0x37/0x3a Leftover inexact backtrace: Inexact backtrace: [<c0405c7...

...: fpu tsc msr pae mce cx8 mtrr mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow up ts bogomips : 9928.70 ? Also I am receiving a kernel-bug message When I try to create a domU BUG: warning at kernel/lockdep.c:1814/trace_hardirqs_on() (Not tainted) [<c040566e>] show_trace_log_lvl+0x58/0x177 [<c0405c73>] show_trace+0xd/0x10 [<c0405cb1>] dump_stack+0x19/0x1b [<c043646e>] trace_hardirqs_on+0xa4/0x120 [<c0404e67>] restore_all+0x37/0x3a DWARF2 unwinder stuck at restore_all+0x37/0x3a Leftover inexact backtrace: Inexact backtrace: [<c0405c7...

This series consists of improvements to Xen''s ability to print traces of its own stack, and specifically for the stack overflow case to be able to use frame pointers in a debug build. I have dev tested the series in debug and non-debug cases, with and without memory guards, and I believe that all the stack traces look correct (given the available information Xen has), and that the

This series consists of improvements to Xen''s ability to print traces of its own stack, and specifically for the stack overflow case to be able to use frame pointers in a debug build. I have dev tested the series in debug and non-debug cases, with and without memory guards, and I believe that all the stack traces look correct. However, I would greatly appreciate a second opinion on the

On Mon, Dec 12, 2016 at 06:54:07PM +0800, Herbert Xu wrote: > On Mon, Dec 12, 2016 at 06:25:12AM +0000, Gonglei (Arei) wrote: > > Hi, Michael & Herbert > > > > Because the virtio-crypto device emulation had been in QEMU 2.8, > > would you please merge the virtio-crypto driver for 4.10 if no other > > comments? If so, Miachel pls ack and/or review the patch,

On Mon, Dec 12, 2016 at 06:54:07PM +0800, Herbert Xu wrote: > On Mon, Dec 12, 2016 at 06:25:12AM +0000, Gonglei (Arei) wrote: > > Hi, Michael & Herbert > > > > Because the virtio-crypto device emulation had been in QEMU 2.8, > > would you please merge the virtio-crypto driver for 4.10 if no other > > comments? If so, Miachel pls ack and/or review the patch,

...happens, does that not Just Work? > > I think I've asked this before... > Rusty. Hi Rusty, setting the (one) virtqueue, vblk is currently using, as broken doesn't solve the problems. In that case virtblk_request()s still succeed - like this one... ([<0000000000112b28>] show_trace+0xf8/0x154) [<0000000000112bde>] show_stack+0x5a/0xdc [<000000000045eb56>] virtblk_request+0x25a/0x2b8 [<00000000003e749c>] __blk_run_queue+0x50/0x64 [<00000000003edb54>] blk_queue_bio+0x358/0x3f0 [<00000000003eb446>] generic_make_request+0xea/0x130 [<0...

...happens, does that not Just Work? > > I think I've asked this before... > Rusty. Hi Rusty, setting the (one) virtqueue, vblk is currently using, as broken doesn't solve the problems. In that case virtblk_request()s still succeed - like this one... ([<0000000000112b28>] show_trace+0xf8/0x154) [<0000000000112bde>] show_stack+0x5a/0xdc [<000000000045eb56>] virtblk_request+0x25a/0x2b8 [<00000000003e749c>] __blk_run_queue+0x50/0x64 [<00000000003edb54>] blk_queue_bio+0x358/0x3f0 [<00000000003eb446>] generic_make_request+0xea/0x130 [<0...

...00000000000000a 0000000000000020 000003ff0000000a [ 20.391426] 000003ff0000000c 000000000c0eb7c8 0000000000000000 0000000000000000 [ 20.391432] 0700000000c173c8 00000000001126ba 000000000c0eb760 000000000c0eb7b8 [ 20.391439] Call Trace: [ 20.391442] ([<000000000011259e>] show_trace+0x8e/0xe0) [ 20.391446] [<0000000000112670>] show_stack+0x80/0xd8 [ 20.391449] [<0000000000753ab6>] dump_stack+0x96/0xd8 [ 20.391453] [<00000000007872e6>] check_preemption_disabled+0xfe/0x128 [ 20.391456] [<0000000000839cc4>] virtio_crypto_ablkcipher_setkey+0...

...f b6 83 36 01 00 RIP [<ffffffff8831b12d>] :ip_conntrack:destroy_conntrack+0x3b/0x112 RSP <ffff81011d6bfe78> CR2: ffffffff88350110 <3>BUG: sleeping function called from invalid context at kernel/rwsem.c:20 in_atomic():0, irqs_disabled():1 Call Trace: [<ffffffff8026999a>] show_trace+0x34/0x47 [<ffffffff802699bf>] dump_stack+0x12/0x17 [<ffffffff8029e64f>] down_read+0x15/0x23 [<ffffffff8029666e>] blocking_notifier_call_chain+0x13/0x36 [<ffffffff8021505c>] do_exit+0x1f/0x8f7 [<ffffffff80264fe6>] do_page_fault+0x7a1/0x81c [<ffffffff8026307d&...

...ne... > > No, you set *all* virtqueues broken. Which is accurate, right? > > Cheers, > Rusty. > I'm sorry, but I don't get this. The vblk involved has only 1 virtqueue. What do you mean by all "*all* virtqueues ? Heinz >> >> ([<0000000000112b28>] show_trace+0xf8/0x154) >> [<0000000000112bde>] show_stack+0x5a/0xdc >> [<000000000045eb56>] virtblk_request+0x25a/0x2b8 >> [<00000000003e749c>] __blk_run_queue+0x50/0x64 >> [<00000000003edb54>] blk_queue_bio+0x358/0x3f0 >> [<00000000003e...

...ne... > > No, you set *all* virtqueues broken. Which is accurate, right? > > Cheers, > Rusty. > I'm sorry, but I don't get this. The vblk involved has only 1 virtqueue. What do you mean by all "*all* virtqueues ? Heinz >> >> ([<0000000000112b28>] show_trace+0xf8/0x154) >> [<0000000000112bde>] show_stack+0x5a/0xdc >> [<000000000045eb56>] virtblk_request+0x25a/0x2b8 >> [<00000000003e749c>] __blk_run_queue+0x50/0x64 >> [<00000000003edb54>] blk_queue_bio+0x358/0x3f0 >> [<00000000003e...

...4.8]# service misdn-init start CAPI Subsystem Rev 1.1.2.8 capifs: Rev 1.1.2.3 capi20: Rev 1.1.2.7: started up with major 68 (middleware+capifs) INFO: trying to register non-static key. the code is fine but needs lockdep annotation. turning off the locking correctness validator. [<c1005d3a>] show_trace_log_lvl+0x1a/0x2f [<c10062e3>] show_trace+0x12/0x14 [<c100635e>] dump_stack+0x16/0x18 [<c10363c7>] __lock_acquire+0x118/0x835 [<c1036de1>] lock_acquire+0x61/0x80 [<c11f58b7>] _spin_lock_irqsave+0x33/0x43 [<c11f54f6>] __down+0x3c/0xbf [<c11f5332&...

Hello I have a lot of problem using the xenbus api (in xen-3.0-testing). I had to modify the network backend driver (file netback.c), and each call to a xenbus function in a virtual machine make my machine reboot (not the virtual, the real machine). for example, I ''ve add this line of code (wich is useless):

...; setting the (one) virtqueue, vblk is currently using, as broken doesn't > solve the problems. > > In that case virtblk_request()s still succeed - like this one... No, you set *all* virtqueues broken. Which is accurate, right? Cheers, Rusty. > > ([<0000000000112b28>] show_trace+0xf8/0x154) > [<0000000000112bde>] show_stack+0x5a/0xdc > [<000000000045eb56>] virtblk_request+0x25a/0x2b8 > [<00000000003e749c>] __blk_run_queue+0x50/0x64 > [<00000000003edb54>] blk_queue_bio+0x358/0x3f0 > [<00000000003eb446>] generic_make_re...

...9:45 testbox kernel: [ 524.585104] Call Trace: Feb 10 10:59:45 testbox kernel: [ 524.585107] [<c07cc721>] ? __schedule_bug+0x5d/0x63 Feb 10 10:59:45 testbox kernel: [ 524.585110] [<c07d277e>] ? schedule+0x69/0x67d Feb 10 10:59:45 testbox kernel: [ 524.585115] [<c0405c90>] ? show_trace_log_lvl+0x40/0x47 Feb 10 10:59:45 testbox kernel: [ 524.585118] [<c0405cae>] ? show_trace+0x17/0x19 Feb 10 10:59:45 testbox kernel: [ 524.585121] [<c07cb105>] ? dump_stack+0x6d/0x73 Feb 10 10:59:45 testbox kernel: [ 524.585124] [<c042e20a>] ? __might_sleep+0xdd/0xe4 Feb 10...

...1/0x41 [<02107326>] do_IRQ+0xf3/0x169 ======================= [<021d9314>] serial8250_console_write+0x0/0x1bc [<021d9314>] serial8250_console_write+0x0/0x1bc [<02123bc0>] kernel_text_address+0x2b/0x37 [<0210605a>] print_context_stack+0x37/0x44 [<021060ba>] show_trace+0x53/0x77 [<02106159>] show_stack+0x7b/0x81 [<02106250>] show_registers+0xde/0x177 [<021063a7>] die+0x59/0xaf [<021146f3>] do_page_fault+0x2f7/0x446 [<02192ba5>] __delay+0x9/0xa [<021d948a>] serial8250_console_write+0x176/0x1bc [<021d9314>] serial82...

...18:36:19 667 pages swap cached Aug 4 18:36:24 1 pages dirty Aug 4 18:36:30 27115 pages writeback Aug 4 18:36:32 1090 pages mapped Aug 4 18:36:36 6800 pages slab Aug 4 18:36:44 695 pages pagetables Aug 4 18:36:51 oom-killer: gfp_mask=0x200d2, order=0 Aug 4 18:36:51 [<c0105801>] show_trace+0x21/0x30 Aug 4 18:36:51 [<c010593e>] dump_stack+0x1e/0x20 Aug 4 18:36:51 [<c0140de0>] out_of_memory+0x90/0xc0 Aug 4 18:36:52 [<c014219d>] __alloc_pages+0x2ed/0x320 Aug 4 18:36:52 [<c014d0c0>] do_wp_page+0xa0/0x4c0 Aug 4 18:36:52 [<c014ddd8>] do_swap_pa...

These patches address issues in the kernel part of xenoprof: * Ill-advised use of on_each_cpu() can lead to sleep with interrupts disabled. * Race conditions in active_domains code. * Cleanup of active_domains code. Comments welcome. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel