search for: lock_timer_base

...37 (NOTLB) f1c87b68 00000082 c30229e0 048c664f 00000e65 f1c87b18 00000007 f7bacaa0 f7d97aa0 048c72fc 00000e65 00000cad 00000003 f7bacbac c302a9e0 c042daae f7d20000 f1c87b70 00000286 ffffffff 00000000 00000000 00ed957a 00ed957a Call Trace: [<c042daae>] lock_timer_base+0x15/0x2f [<c0604dfc>] schedule_timeout+0x71/0x8c [<c042d1d3>] process_timeout+0x0/0x5 [<c04803a8>] do_select+0x371/0x3cb [<c048092b>] __pollwait+0x0/0xb2 [<c04202b1>] default_wake_function+0x0/0xc [<c04202b1>] default_wake_function+0x0/0xc [<c06046b9&g...

I have a sles10sp3 vm that I''m trying to passthrough a scsi card, which has a DLT tape drive attached. Anyone doing anything similar? When I passthrough the scsi card (forced to do both ports), the vm dies when it loads, I think during udev. I''m viewing the vm through virt-manager, so I can''t scroll up and see what everything says. Is there a way to get the text xm

...6e1af8 Call Trace: [<ffffffff811ada77>] ? __set_page_dirty+0x87/0xf0 [<ffffffff810923be>] ? prepare_to_wait+0x4e/0x80 [<ffffffffa01e881f>] jbd2_journal_commit_transaction+0x19f/0x14b0 [jbd2] [<ffffffff810096f0>] ? __switch_to+0xd0/0x320 [<ffffffff8107e00c>] ? lock_timer_base+0x3c/0x70 [<ffffffff810920d0>] ? autoremove_wake_function+0x0/0x40 [<ffffffffa01eef78>] kjournald2+0xb8/0x220 [jbd2] [<ffffffff810920d0>] ? autoremove_wake_function+0x0/0x40 [<ffffffffa01eeec0>] ? kjournald2+0x0/0x220 [jbd2] [<ffffffff81091d66>] kthread+0x96/...

...d136f656>] ip6_output+0x9c7/0x9f3 [ipv6] [<d137c8c0>] dst_output+0x0/0x7 [ipv6] [<c05c3d12>] nf_hook_slow+0x3a/0x90 [<d137c8c0>] dst_output+0x0/0x7 [ipv6] [<d137e4d6>] ndisc_send_ns+0x3a8/0x47a [ipv6] [<c06090d8>] _spin_lock_irqsave+0x8/0x28 [<c042914a>] lock_timer_base+0x15/0x2f [<d1375ddb>] addrconf_dad_timer+0xc3/0xdf [ipv6] [<c0434244>] hrtimer_run_queues+0x14b/0x163 [<d1375d18>] addrconf_dad_timer+0x0/0xdf [ipv6] [<c0429600>] run_timer_softirq+0x101/0x15c [<c042613e>] __do_softirq+0x5e/0xc3 [<c0406edf>] do_softirq+0x5...

...a0a>] __wait_on_bit+0x40/0x6e [<ffffffff800155a2>] sync_buffer+0x0/0x3f [<ffffffff80063aa4>] out_of_line_wait_on_bit+0x6c/0x78 [<ffffffff800a34d6>] wake_bit_function+0x0/0x23 [<ffffffff88033e56>] :jbd:journal_commit_transaction+0x968/0x10c2 [<ffffffff8003d7d9>] lock_timer_base+0x1b/0x3c [<ffffffff880376a3>] :jbd:kjournald+0xc1/0x213 [<ffffffff800a34a8>] autoremove_wake_function+0x0/0x2e [<ffffffff880375e2>] :jbd:kjournald+0x0/0x213 [<ffffffff800a3290>] keventd_create_kthread+0x0/0xc4 [<ffffffff8003264c>] kthread+0xfe/0x132 [<fffffff...

...8819] Pid: 11, comm: xenwatch Tainted: G W O 3.3.5-1.pvops.qubes.x86_64 #1 [ 1257.228825] Call Trace: [ 1257.228830] [<ffffffff810495aa>] warn_slowpath_common+0x7a/0xb0 [ 1257.228836] [<ffffffff81049681>] warn_slowpath_fmt+0x41/0x50 [ 1257.228842] [<ffffffff81057ba7>] ? lock_timer_base+0x37/0x70 [ 1257.228850] [<ffffffff811a7433>] sysfs_attr_ns+0x93/0xa0 [ 1257.228856] [<ffffffff811a7aef>] sysfs_remove_file+0x1f/0x40 [ 1257.228862] [<ffffffff812e5622>] device_remove_file+0x12/0x20 [ 1257.228870] [<ffffffffa00faf5a>] xennet_remove+0x84/0xac [xen_netfron...

...6/0x250 [fbcon] Sep 17 15:26:18 box6 kernel: [ 1948.826145] [<ffffffff810397a9>] ? default_spin_lock_flags+0x9/0x10 Sep 17 15:26:18 box6 kernel: [ 1948.826148] [<ffffffff8155aa2f>] ? _spin_lock_irqsave+0x2f/0x40 Sep 17 15:26:18 box6 kernel: [ 1948.826154] [<ffffffff81076c7c>] ? lock_timer_base+0x3c/0x70 Sep 17 15:26:18 box6 kernel: [ 1948.826157] [<ffffffff81077d17>] ? mod_timer+0x147/0x230 Sep 17 15:26:18 box6 kernel: [ 1948.826161] [<ffffffff8134350e>] do_unblank_screen+0x9e/0x170 Sep 17 15:26:18 box6 kernel: [ 1948.826165] [<ffffffff813435f0>] unblank_screen+0x10/...

...f88a7846 Call Trace: [<f88a9781>] __journal_remove_checkpoint+0x56/0x75 [jbd] [<f88a8f61>] __try_to_free_cp_buf+0x31/0x68 [jbd] [<f88a9700>] __journal_clean_checkpoint_list+0x6f/0x9a [jbd] [<f88a7846>] journal_commit_transaction+0x147/0xff1 [jbd] [<c01295f7>] lock_timer_base+0x15/0x2f [<c0129803>] try_to_del_timer_sync+0x45/0x4d [<f88aa68b>] kjournald+0xc5/0x20d [jbd] [<f88aa5c0>] commit_timeout+0x0/0x5 [jbd] [<c01347c2>] autoremove_wake_function+0x0/0x37 [<f88aa5c6>] kjournald+0x0/0x20d [jbd] [<c0101ca1>] kernel_thread_h...

...kernel: nvkm_vmm_map+0x1a5/0x3e0 [nouveau] feb 23 17:21:08 dell-2017 kernel: ? gp100_vmm_pgt_sgl+0x180/0x180 [nouveau] feb 23 17:21:08 dell-2017 kernel: nvkm_vram_map+0x43/0x50 [nouveau] feb 23 17:21:08 dell-2017 kernel: nvkm_uvmm_mthd+0x71e/0x850 [nouveau] feb 23 17:21:08 dell-2017 kernel: ? lock_timer_base+0x62/0x80 feb 23 17:21:08 dell-2017 kernel: nvkm_ioctl+0x105/0x240 [nouveau] feb 23 17:21:08 dell-2017 kernel: nvif_object_mthd+0xd3/0xf0 [nouveau] feb 23 17:21:08 dell-2017 kernel: ? dma_fence_wait_timeout+0x30/0x30 feb 23 17:21:08 dell-2017 kernel: nvif_vmm_map+0xef/0x110 [nouveau] feb 23 17:...

I suspect this might be related to previous btrfs errors I''ve had on the same filesystem. See: http://python.ca/nas/linux/btrfs_bug.txt The most recent kernel message is: WARNING: at fs/btrfs/extent-tree.c:8239 btrfs_free_block_groups+0x218/0x275() Hardware name: MS-7388 Modules linked in: udf crc_itu_t isofs loop nls_iso8859_1 vboxnetflt vboxdrv nls_utf8 nls_cp437

...ff80063aa4>] out_of_line_wait_on_bit+0x6c/0x78 May 2 22:48:20 vmail kernel: [<ffffffff800a34d5>] wake_bit_function+0x0/0x23 May 2 22:48:20 vmail kernel: [<ffffffff88033a47>] :jbd:journal_commit_transaction+0x559/0x10c2 May 2 22:48:20 vmail kernel: [<ffffffff8003d7be>] lock_timer_base+0x1b/0x3c May 2 22:48:20 vmail kernel: [<ffffffff8004ad59>] try_to_del_timer_sync+0x7f/0x88 May 2 22:48:20 vmail kernel: [<ffffffff880376a3>] :jbd:kjournald+0xc1/0x213 May 2 22:48:20 vmail kernel: [<ffffffff800a34a7>] autoremove_wake_function+0x0/0x2e May 2 22:48:20 vmai...

...f880118868048 [ 828.042724] Call Trace: [ 828.044071] [<ffffffff8109d141>] ? cpuacct_charge+0x61/0x70 [ 828.045445] [<ffffffff8108dd88>] ? __enqueue_entity+0x78/0x80 [ 828.046829] [<ffffffff810920f6>] ? enqueue_entity+0x286/0xa20 [ 828.048227] [<ffffffff81065bbb>] ? lock_timer_base.isra.35+0x2b/0x50 [ 828.049648] [<ffffffff814c6f09>] schedule+0x29/0x70 [ 828.051076] [<ffffffffa0468695>] wait_current_trans.isra.14+0xa5/0xf0 [btrfs] [ 828.052515] [<ffffffff8107b460>] ? wake_up_bit+0x30/0x30 [ 828.053970] [<ffffffffa0469e18>] start_transaction+0x3...

I''ve been working on running down intermittent ENOSPC issues. I can only seem to replicate ENOSPC errors when running zlib compression. However, I have been seeing similar ENOSPC errors to a lesser extent when playing with the LZ4HC patches. I apologize for not following up on this sooner, but I had drifted away from using zlib, and didn''t notice there was still an issue. My

Hi, Is anybody know the purpose of this method (xen_evtchn_do_upcall)? When I run a user level application involved in TCP receiving and the SoftIRQ for eth0 on the same CPU core, everything is OK. But if I run them on 2 different cores, there will be xen_evtchn_do_upcall() existing (maybe when the local_bh_disable<http://www.cs.fsu.edu/~baker/devices/lxr/http/ident?i=local_bh_disable>() or

On Wed, 2016-02-03 at 15:28 -0500, Konrad Rzeszutek Wilk wrote: > > > And I wonder if the XEN_DOMCTL_irq_permission aka, > > > xc_domain_irq_permission > > > had been called. I remember that at some point we missed it for > > > Xend.. > > > > > False alarm. > > It was all in Linux. Attached are four patches (the first two > are for

...> >>> rb_insert_color+0xa4/0x140 > >>> Feb 14 02:05:52 lupus kernel: [   70.057766]  [<ffffffff8134b0b6>] > ? > >>> tree_insert+0x86/0x1e0 > >>> Feb 14 02:05:52 lupus kernel: [   70.057859]  [<ffffffff81058c73>] > ? > >>> lock_timer_base.clone.22+0x33/0x70 > >>> Feb 14 02:05:52 lupus kernel: [   70.058004]  [<ffffffff81305060>] > ? > >>> btree_get_extent+0x0/0x1c0 > >>> Feb 14 02:05:52 lupus kernel: [   70.058097]  [<ffffffff81330b21>] > ? > >>> read_extent_buffer_pa...

...race: Apr 11 04:24:05 xenserver kernel: [277210.437757] <IRQ> [<ffffffff8022c9a2>] warn_on_slowpath+0x51/0x78 Apr 11 04:24:05 xenserver kernel: [277210.437774] [<ffffffff8022d4f4>] printk+0x4e/0x56 Apr 11 04:24:05 xenserver kernel: [277210.437784] [<ffffffff80235a70>] lock_timer_base+0x26/0x4b Apr 11 04:24:05 xenserver kernel: [277210.437794] [<ffffffff80235c16>] __mod_timer+0xd4/0xe3 Apr 11 04:24:05 xenserver kernel: [277210.437804] [<ffffffff8023ca2f>] queue_delayed_work_on+0xb8/0xc8 Apr 11 04:24:05 xenserver kernel: [277210.437813] [<ffffffff803d8161>]...

I''m currently working on moving storage services into their own domain and I''ve been looking at blktap2. I''ve been trying to get an image mounted with blktap2 and for some odd reason and tapdisk2 keeps hanging instead of quitting at the end. I haven''t removed any of the storage startup code at this point so everything should be as it normally is in xen-unstable.

On Sun, Nov 07 2010 at 6:05pm -0500, Andi Kleen <andi@firstfloor.org> wrote: > On Sun, Nov 07, 2010 at 10:39:23PM +0100, Milan Broz wrote: > > On 11/07/2010 08:45 PM, Andi Kleen wrote: > > >> I read about barrier-problems and data getting to the partition when > > >> using dm-crypt and several layers so I don''t know if that could be > >

Greetings, I got the below dmesg and the first bad commit is commit cf39c8e5352b4fb9efedfe7e9acb566a85ed847c Merge: 3398d25 23b7eaf Author: Linus Torvalds <torvalds@linux-foundation.org> Date: Wed Sep 4 17:45:39 2013 -0700 Merge tag ''stable/for-linus-3.12-rc0-tag'' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip Pull Xen updates from Konrad