search for: system_call

...22:02:59 lh10 kernel: <ffffffffa00d6196>{:st:st_write+2692} <ffffffff80194b39>{inode_update_time+159} Mar 22 22:02:59 lh10 kernel: <ffffffff8017beaa>{vfs_write+207} <ffffffff8017bf92>{sys_write+69} Mar 22 22:02:59 lh10 kernel: <ffffffff801102f6>{system_call+126} Mar 22 22:02:59 lh10 kernel: Trying to fix it up, but a reboot is needed Mar 22 22:02:59 lh10 kernel: Bad page state at free_hot_cold_page (in process 'star', page 000001023eb70ed8) Mar 22 22:02:59 lh10 kernel: flags:0x0100000c mapping:00000102146a4240 mapcount:2 count:0 Mar 22 22:02:...

...t; <ffffffff8011c21a>{flush_tlb_page+44} <5> <ffffffff80169106>{do_wp_page+1127} <ffffffff80123ed3>{do_page_fault+575} <5> <ffffffff80169ff2>{handle_mm_fault+1228} <ffffffff80123e9a>{do_page_fault+518} <5> <ffffffff8011026a>{system_call+126} <ffffffff80132bc6>{schedule_tail+202} <5> <ffffffff80110d91>{error_exit+0} <5> <5> Code: 8b 40 10 89 44 24 58 e8 3d 80 1a e0 31 c0 f6 44 24 58 07 0f <5> RIP <ffffffffa0163207>{:wct4xxp:t4_interrupt_gen2+63} RSP <00000100013ebdb0> <5>...

...waff [<ffffffff802220b0>] copy_process+0xc50/0x1870 1 20:53:48 waff [<ffffffff8023680f>] do_fork+0xef/0x210 1 20:53:48 waff [<ffffffff8029c652>] recalc_sigpending+0x12/0x20 1 20:53:48 waff [<ffffffff8022005d>] sigprocmask+0xfd/0x110 1 20:53:48 waff [<ffffffff80269662>] system_call+0x86/0x8b 1 20:53:48 waff [<ffffffff802767c3>] sys_clone+0x23/0x30 1 20:53:48 waff [<ffffffff80269a71>] ptregscall_common+0x3d/0x64 1 20:53:48 waff 1 20:53:48 waff 1 20:53:48 waff Code: 0f 0b 68 b8 76 5a 80 c2 c5 00 90 c9 c3 00 00 00 00 00 00 00 1 20:53:48 waff RIP [<ffffffff8028...

...4] [do_get_write_access+1382/1420] [v1_read_dqblk+121/196] [read_dqblk+76/128] [dqget+344/484] [vfs_get_dqblk+21/64] [v1_get_dqblk+39/172] [link_path_walk+2680/2956] [do_compat_quotactl+417/688] [resolve_dev+89/108] [sys_quotactl+166/275] [system_call+51/56] So it is trying to start a transaction to update the atime on the quota file, and has a lock on some quota structures thanks to "read_dqblk". At the same time, "sync" is running: sync Call Trace: [__down+109/208] [__down_failed+8/12] [.text.lo...

...hed-messaging [kernel.vmlinux] [k] mutex_unlock 3.89% sched-messaging [kernel.vmlinux] [k] wait_consider_task 3.64% sched-messaging [kernel.vmlinux] [k] _raw_write_lock_irq 3.41% sched-messaging [kernel.vmlinux] [k] mutex_spin_on_owner.is 2.49% sched-messaging [kernel.vmlinux] [k] system_call after patch: 9.99% sched-messaging [kernel.vmlinux] [k] mutex_unlock 5.28% sched-messaging [unknown] [H] 0xc0000000000768e0 4.27% sched-messaging [kernel.vmlinux] [k] __copy_tofrom_user_power7 3.77% sched-messaging [kernel.vmlinux] [k] copypage_power7 3.24% sched-messaging...

...hed-messaging [kernel.vmlinux] [k] mutex_unlock 3.89% sched-messaging [kernel.vmlinux] [k] wait_consider_task 3.64% sched-messaging [kernel.vmlinux] [k] _raw_write_lock_irq 3.41% sched-messaging [kernel.vmlinux] [k] mutex_spin_on_owner.is 2.49% sched-messaging [kernel.vmlinux] [k] system_call after patch: 9.99% sched-messaging [kernel.vmlinux] [k] mutex_unlock 5.28% sched-messaging [unknown] [H] 0xc0000000000768e0 4.27% sched-messaging [kernel.vmlinux] [k] __copy_tofrom_user_power7 3.77% sched-messaging [kernel.vmlinux] [k] copypage_power7 3.24% sched-messaging...

I implemented sysenter for 32-on-64, since it seemed straightforward enough. It mostly works, but every now and again I get vcpus just hanging in blocked state, as if events are being lost or ignored. Its very similar to the symptoms that other people have reported against the pvops kernel, which I have not managed to reproduce. Perhaps using sysenter is exacerbating an existing bug...

...hed-messaging [kernel.vmlinux] [k] mutex_unlock 3.89% sched-messaging [kernel.vmlinux] [k] wait_consider_task 3.64% sched-messaging [kernel.vmlinux] [k] _raw_write_lock_irq 3.41% sched-messaging [kernel.vmlinux] [k] mutex_spin_on_owner.is 2.49% sched-messaging [kernel.vmlinux] [k] system_call We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. These spin_on_onwer variant also cause rcu stall before we apply this patch set Pan Xinhui (4): kernel/sched: introduce vcpu preempted check interface...

...hed-messaging [kernel.vmlinux] [k] mutex_unlock 3.89% sched-messaging [kernel.vmlinux] [k] wait_consider_task 3.64% sched-messaging [kernel.vmlinux] [k] _raw_write_lock_irq 3.41% sched-messaging [kernel.vmlinux] [k] mutex_spin_on_owner.is 2.49% sched-messaging [kernel.vmlinux] [k] system_call We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. These spin_on_onwer variant also cause rcu stall before we apply this patch set Pan Xinhui (4): kernel/sched: introduce vcpu preempted check interface...

...changes. Convert them to preprocessor macros. Signed-off-by: Josh Poimboeuf <jpoimboe at redhat.com> --- arch/x86/entry/entry_32.S | 12 +++--- arch/x86/entry/entry_64.S | 10 ++--- arch/x86/entry/entry_64_compat.S | 8 ++-- arch/x86/entry/vdso/vdso32/system_call.S | 10 ++--- arch/x86/include/asm/alternative-asm.h | 68 +++++++++++++++----------------- arch/x86/include/asm/smap.h | 4 +- arch/x86/lib/copy_page_64.S | 2 +- arch/x86/lib/memcpy_64.S | 4 +- arch/x86/lib/memmove_64.S | 3 +- arch/...

...tart_229} <ffffffff801ee571>{ext3_dirty_inode+113} <ffffffff801a5604>{__mark_inode_dirty+52} <ffffffff8019bd2b>{update_atime+123} <ffffffff80195016>{vfs_readdir+166} <ffffffff801952e2>{syst_getdents+130} <ffffffff8019465e>{sys_fcntl+830} <ffffffff8010dc46>{system_call+126} Code: 8b 40 18 48 c1 e0 07 48 8b 98 08 58 5b 80 4c 01 e3 48 89 df RIP <ffffffff8012f369>{try_to_wake_up+57} RSP <ffff810004827e88> <0>Kernel panic - not syncing: Aiee, killing interrupt handler! -- Maurice Volaski, mvolaski at aecom.yu.edu Computing Support, Rose F. Kenned...

...function+0x0/0xe [<ffffffff803f0976>] __down_read+0x12/0xec [<ffffffff88021120>] :fuse:fuse_dev_read+0x1a/0x1f [<ffffffff802804bc>] vfs_read+0xcb/0x171 [<ffffffff802274c7>] default_wake_function+0x0/0xe [<ffffffff8028089b>] sys_read+0x45/0x6e [<ffffffff8020a436>] system_call+0x86/0x8b [<ffffffff8020a3b0>] system_call+0x0/0x8b Code: 48 89 42 08 48 89 10 48 c7 41 08 00 02 20 00 f6 46 30 08 48 RIP [<ffffffff88020838>] :fuse:request_end+0x45/0x109 RSP <ffff88001f04dd68> CR2: 0000000000100108 dovecot01gluster01 kernel: Oops: 0002 [1] SMP...

...a608>] vhost_net_ioctl+0x510/0x570 [vhost_net] [ 55.951924] [<0000001ede3c4dd8>] do_vfs_ioctl+0x430/0x6f8 [ 55.951926] [<0000001ede3c5124>] ksys_ioctl+0x84/0xb0 [ 55.951927] [<0000001ede3c51ba>] __s390x_sys_ioctl+0x2a/0x38 [ 55.951931] [<0000001edeb27f72>] system_call+0x2a6/0x2c8 [ 55.951949] CPU: 34 PID: 1908 Comm: CPU 0/KVM Not tainted 5.5.0+ #21 [ 55.951950] Hardware name: IBM 3906 M04 704 (LPAR) [ 55.951951] Call Trace: [ 55.951952] [<0000001ede114132>] show_stack+0x8a/0xd0 [ 55.951954] [<0000001edeb0672a>] dump_stack+0x8a/0xb8 [...

...0x570 [vhost_net] >> [ 55.951924] [<0000001ede3c4dd8>] do_vfs_ioctl+0x430/0x6f8 >> [ 55.951926] [<0000001ede3c5124>] ksys_ioctl+0x84/0xb0 >> [ 55.951927] [<0000001ede3c51ba>] __s390x_sys_ioctl+0x2a/0x38 >> [ 55.951931] [<0000001edeb27f72>] system_call+0x2a6/0x2c8 >> [ 55.951949] CPU: 34 PID: 1908 Comm: CPU 0/KVM Not tainted 5.5.0+ #21 >> [ 55.951950] Hardware name: IBM 3906 M04 704 (LPAR) >> [ 55.951951] Call Trace: >> [ 55.951952] [<0000001ede114132>] show_stack+0x8a/0xd0 >> [ 55.951954] [<0000...

...14006/37792] [get_new_inode+197/312] [iget4+117/128] [__brelse+29/192] [iget+22/32] [ext3_lookup+90/140] [real_lookup+91/180] [permission+32/56] [lookup_dentry+304/504] [__fput+74/84] [open_namei+105/776] [fput+70/84] [filp_open+74/264] [filp_open+17/264] [sys_open+63/160] [sys_open+38/160] [system_call+52/56] Code: 8b 47 08 3d 2b 2f c3 a5 0f 85 be 01 00 00 f6 46 05 01 0f 85 May 2 11:32:00 - While issuing an du -sk on an ext3 filesystem. du -sk segfaulted. Unable to handle kernel paging request at virtual address 8ec91fc8 current->tss.cr3 = 0b130000, %%cr3 = 0b130000 *pde = 00000000...

...ex_unlock >> 3.89% sched-messaging [kernel.vmlinux] [k] wait_consider_task >> 3.64% sched-messaging [kernel.vmlinux] [k] _raw_write_lock_irq >> 3.41% sched-messaging [kernel.vmlinux] [k] mutex_spin_on_owner.is >> 2.49% sched-messaging [kernel.vmlinux] [k] system_call >> >> We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin >> loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. >> These spin_on_onwer variant also cause rcu stall before we apply this patch set >> > Paolo, could you help out...

...ex_unlock >> 3.89% sched-messaging [kernel.vmlinux] [k] wait_consider_task >> 3.64% sched-messaging [kernel.vmlinux] [k] _raw_write_lock_irq >> 3.41% sched-messaging [kernel.vmlinux] [k] mutex_spin_on_owner.is >> 2.49% sched-messaging [kernel.vmlinux] [k] system_call >> >> We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin >> loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. >> These spin_on_onwer variant also cause rcu stall before we apply this patch set >> > Paolo, could you help out...

...mutex_unlock >> 3.89% sched-messaging [kernel.vmlinux] [k] wait_consider_task >> 3.64% sched-messaging [kernel.vmlinux] [k] _raw_write_lock_irq >> 3.41% sched-messaging [kernel.vmlinux] [k] mutex_spin_on_owner.is >> 2.49% sched-messaging [kernel.vmlinux] [k] system_call >> >> We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin >> loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. >> These spin_on_onwer variant also cause rcu stall before we apply this patch set >> > > Paolo, could you hel...

...mutex_unlock >> 3.89% sched-messaging [kernel.vmlinux] [k] wait_consider_task >> 3.64% sched-messaging [kernel.vmlinux] [k] _raw_write_lock_irq >> 3.41% sched-messaging [kernel.vmlinux] [k] mutex_spin_on_owner.is >> 2.49% sched-messaging [kernel.vmlinux] [k] system_call >> >> We introduce interface bool vcpu_is_preempted(int cpu) and use it in some spin >> loops of osq_lock, rwsem_spin_on_owner and mutex_spin_on_owner. >> These spin_on_onwer variant also cause rcu stall before we apply this patch set >> > > Paolo, could you hel...

...dev/sda1 Reboot / power on It auto mounts the /dev/sda2 as ext4 on /mnt/disc/sda2 $ umount /mnt/disc/sda2 $ mkdir /root/foo $ mke2fs /dev/sda2 $ mount /dev/sda2 /root/foo Kernel panic Snip from the kernel panic: ?????? list_del+0xb/0x71 cache_alloc_refill+0xf1/0x186 ext2_fill_super+0x0/0xa37 .... system_call+0x7e/0x83 -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x...