search for: sys_read

Displaying 20 results from an estimated 66 matches for "sys_read".

2005 Jan 14
1
xen-unstable dom0/1 smp schedule while atomic
...was running in dom0 and I remotely initiated an scp from dom0 to another remote host (not dom1) Ill only post the first and last few "scheduling while atomic" entries, let me know if someone wants the whole trace. scheduling while atomic [schedule+1682/1696] schedule+0x692/0x6a0 [sys_read+126/128] sys_read+0x7e/0x80 [work_resched+5/47] work_resched+0x5/0x2f scheduling while atomic [schedule+1682/1696] schedule+0x692/0x6a0 [sys_read+126/128] sys_read+0x7e/0x80 [work_resched+5/47] work_resched+0x5/0x2f scheduling while atomic [schedule+1682/1696] schedule+0x692/0x6a0 [do...
2005 Nov 01
2
xen, lvm, drbd, bad kernel messages
...1 13:52:13 localhost kernel: [autoremove_wake_function+0/96] autoremove_wake_function+0x0/0x60 Nov 1 13:52:13 localhost kernel: [generic_file_read+0/208] generic_file_read+0x0/0xd0 Nov 1 13:52:13 localhost kernel: [vfs_read+174/304] vfs_read+0xae/ 0x130 Nov 1 13:52:13 localhost kernel: [sys_read+81/128] sys_read+0x51/0x80 Nov 1 13:52:13 localhost kernel: [syscall_call+7/11] syscall_call +0x7/0xb Nov 1 13:52:13 localhost kernel: Badness in blk_remove_plug at drivers/block/ll_rw_blk.c:1238 Nov 1 13:52:13 localhost kernel: [blk_remove_plug+110/112] blk_remove_plug+0x6e/0x70 Nov 1 1...
2004 May 04
0
rsync 2.6.2 appears to hang
...= 1 [pid 9977] signal(10, 0x00000001 <unfinished ...> [pid 9944] <... select resumed> ) = 1 [pid 9944] read(3, <unfinished ...> [pid 9977] SYS_rt_sigaction(10, 0xbfffa1e0, 0xbfffa150, 8, 10) = 0 [pid 9944] SYS_read(3, <unfinished ...> [pid 9977] <... signal resumed> ) = 0x08051d50 [pid 9944] <... SYS_read resumed> "C", 4) = 4 [pid 9977] signal(12, 0x00000001 <unfinished ...> [pid 9944] <... read resum...
2008 Jul 22
2
pv_ops - 2.6.26 - unable to handle kernel paging request
...__alloc_pages+0xf/0x20 [<c015f4bf>] __get_free_pages+0xf/0x20 [<c01c015f>] proc_file_read+0x8f/0x2a0 [<c01c00d0>] proc_file_read+0x0/0x2a0 [<c01bb7ca>] proc_reg_read+0x5a/0x90 [<c01801f1>] vfs_read+0xa1/0x160 [<c01bb770>] proc_reg_read+0x0/0x90 [<c0180551>] sys_read+0x41/0x70 [<c0107256>] syscall_call+0x7/0xb ======================= Code: cb 77 6f 8b 44 24 1c 89 de c1 e0 03 89 44 24 04 eb 07 83 c6 20 39 f5 72 59 f6 46 02 04 74 f3 8d 4e 18 8b 56 18 8b 41 04 8b 5e 0c <89> 10 89 42 04 8d 04 9b c7 46 18 00 01 10 00 8d 04 43 8b 14 24 EIP: [<c015e22...
2008 Jul 22
2
pv_ops - 2.6.26 - unable to handle kernel paging request
...__alloc_pages+0xf/0x20 [<c015f4bf>] __get_free_pages+0xf/0x20 [<c01c015f>] proc_file_read+0x8f/0x2a0 [<c01c00d0>] proc_file_read+0x0/0x2a0 [<c01bb7ca>] proc_reg_read+0x5a/0x90 [<c01801f1>] vfs_read+0xa1/0x160 [<c01bb770>] proc_reg_read+0x0/0x90 [<c0180551>] sys_read+0x41/0x70 [<c0107256>] syscall_call+0x7/0xb ======================= Code: cb 77 6f 8b 44 24 1c 89 de c1 e0 03 89 44 24 04 eb 07 83 c6 20 39 f5 72 59 f6 46 02 04 74 f3 8d 4e 18 8b 56 18 8b 41 04 8b 5e 0c <89> 10 89 42 04 8d 04 9b c7 46 18 00 01 10 00 8d 04 43 8b 14 24 EIP: [<c015e22...
2014 Nov 03
1
dmesg error
...<ffffffff80016eb7>] generic_file_aio_read+0x36/0x3b [<ffffffff8000cf39>] do_sync_read+0xc7/0x104 [<ffffffff800a34a7>] autoremove_wake_function+0x0/0x2e [<ffffffff80063002>] thread_return+0x62/0xfe [<ffffffff8000b721>] vfs_read+0xcb/0x171 [<ffffffff80011d15>] sys_read+0x45/0x6e [<ffffffff8005d28d>] tracesys+0xd5/0xe0 What should be done? jerry
2017 Jun 05
0
BUG: KASAN: use-after-free in free_old_xmit_skbs
...+0x4e0/0x960 > > [ 310.135351] ? kvm_clock_get_cycles+0x1e/0x20 > > [ 310.136160] ? __vfs_read+0x950/0x950 > > [ 310.136931] ? rw_verify_area+0xbd/0x2b0 > > [ 310.137711] vfs_write+0x155/0x4b0 > > [ 310.138454] SyS_write+0xf7/0x240 > > [ 310.139183] ? SyS_read+0x240/0x240 > > [ 310.139922] ? SyS_read+0x240/0x240 > > [ 310.140649] do_syscall_64+0x235/0x5b0 > > [ 310.141390] ? trace_raw_output_sys_exit+0xf0/0xf0 > > [ 310.142204] ? syscall_return_slowpath+0x240/0x240 > > [ 310.143018] ? trace_do_page_fault+0xc4/0x3a0...
2017 Jun 05
0
BUG: KASAN: use-after-free in free_old_xmit_skbs
...+0x4e0/0x960 > > [ 310.135351] ? kvm_clock_get_cycles+0x1e/0x20 > > [ 310.136160] ? __vfs_read+0x950/0x950 > > [ 310.136931] ? rw_verify_area+0xbd/0x2b0 > > [ 310.137711] vfs_write+0x155/0x4b0 > > [ 310.138454] SyS_write+0xf7/0x240 > > [ 310.139183] ? SyS_read+0x240/0x240 > > [ 310.139922] ? SyS_read+0x240/0x240 > > [ 310.140649] do_syscall_64+0x235/0x5b0 > > [ 310.141390] ? trace_raw_output_sys_exit+0xf0/0xf0 > > [ 310.142204] ? syscall_return_slowpath+0x240/0x240 > > [ 310.143018] ? trace_do_page_fault+0xc4/0x3a0...
2006 Feb 09
1
[Bug 445] New: ipt_account reports: sleeping function called from invalid context at mm/slab.c:2063
...sabled():0 Call Trace:<ffffffff80131dd7>{__might_sleep+173} <ffffffff8015fcab>{kmem_cache_alloc+34} <ffffffffa01b7130>{:ipt_account:account_seq_start+51} <ffffffff80193624>{seq_read+235} <ffffffff801770bf>{vfs_read+207} <ffffffff80177316>{sys_read+69} <ffffffff80110092>{system_call+126} If I move the kmalloc and kfree in account_seq_start and account_seq_stop to outside the spin-lock, these messages go away. I don't see that the lock does anything to protect the malloc/free. My changed version of these functions are: static v...
2016 May 25
3
[PATCH] x86/paravirt: Do not trace _paravirt_ident_*() functions
...t_string+0x5/0x10 [<ffffffff8129dec5>] ? seq_read+0x305/0x370 [<ffffffff81279668>] __vfs_read+0x28/0xe0 [<ffffffff81279645>] ? __vfs_read+0x5/0xe0 [<ffffffff81279645>] ? __vfs_read+0x5/0xe0 [<ffffffff81279df6>] vfs_read+0x86/0x130 [<ffffffff8127b216>] SyS_read+0x46/0xa0 [<ffffffff81cc6176>] entry_SYSCALL_64_fastpath+0x1e/0xa8 Code: 12 48 c1 ea 0c 83 e8 01 83 e2 30 48 98 48 81 c2 40 6d 01 00 48 03 14 c5 80 6a 5d 82 48 89 0a 8b 41 08 85 c0 75 09 f3 90 8b 41 08 <85> c0 74 f7 4c 8b 09 4d 85 c9 74 08 41 0f 18 09 eb 02 f3 90 8b Reported-by: ?...
2016 May 25
3
[PATCH] x86/paravirt: Do not trace _paravirt_ident_*() functions
...t_string+0x5/0x10 [<ffffffff8129dec5>] ? seq_read+0x305/0x370 [<ffffffff81279668>] __vfs_read+0x28/0xe0 [<ffffffff81279645>] ? __vfs_read+0x5/0xe0 [<ffffffff81279645>] ? __vfs_read+0x5/0xe0 [<ffffffff81279df6>] vfs_read+0x86/0x130 [<ffffffff8127b216>] SyS_read+0x46/0xa0 [<ffffffff81cc6176>] entry_SYSCALL_64_fastpath+0x1e/0xa8 Code: 12 48 c1 ea 0c 83 e8 01 83 e2 30 48 98 48 81 c2 40 6d 01 00 48 03 14 c5 80 6a 5d 82 48 89 0a 8b 41 08 85 c0 75 09 f3 90 8b 41 08 <85> c0 74 f7 4c 8b 09 4d 85 c9 74 08 41 0f 18 09 eb 02 f3 90 8b Reported-by: ?...
2012 Oct 24
1
Nouveau soft lockup after switcheroo'd...
.../0xc0 [<ffffffff813887bb>] do_fb_ioctl+0x59b/0x5f0 [<ffffffff81152883>] ? vma_interval_tree_insert+0x83/0x90 [<ffffffff81388af5>] fb_ioctl+0x45/0x50 [<ffffffff8119adda>] do_vfs_ioctl+0x8a/0x340 [<ffffffff8119b121>] sys_ioctl+0x91/0xb0 [<ffffffff81189862>] ? sys_read+0x52/0xa0 [<ffffffff816b9899>] system_call_fastpath+0x16/0x1b Code: ff 00 00 01 00 76 0a 0f b7 d7 ed 5d c3 0f 1f 40 00 48 c7 c6 81 4b a5 81 e8 24 fe ff ff b8 ff ff ff ff 5d c3 0f 1f 44 00 00 8b 07 <5d> c3 0f 1f 40 00 55 48 81 ff ff ff 03 00 48 89 e5 77 2b 48 81 -- Daniel J Blueman
2014 Mar 11
0
kernel panic when using root from virtfs
...lt;ffffffff8110a1ca>] generic_file_aio_read+0x2ca/0x700 [ 14.640174] [<ffffffff811a11f6>] blkdev_aio_read+0x46/0x70 [ 14.640174] [<ffffffff8116c355>] do_sync_read+0x55/0x90 [ 14.640174] [<ffffffff8116c9e0>] vfs_read+0x90/0x160 [ 14.640174] [<ffffffff8116d4e4>] SyS_read+0x44/0xa0 [ 14.640174] [<ffffffff816ab07d>] system_call_fastpath+0x1a/0x1f [ 14.640174] Code: 38 31 c0 66 66 90 c6 01 00 66 66 90 85 c0 0f 85 bf 00 00 00 49 63 fc 48 8d 7c 39 ff 48 31 f9 48 f7 c1 00 f0 ff ff 74 11 66 66 90 <c6> 07 00 66 66 90 85 c0 0f 85 c6 00 00 00 65 ff 04 25 e0...
2011 Feb 18
6
[Bug 34430] New: nouveau driver does not return VGA connector status breaking upower
https://bugs.freedesktop.org/show_bug.cgi?id=34430 Summary: nouveau driver does not return VGA connector status breaking upower Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau
2014 Nov 26
1
[PATCH v12 09/11] pvqspinlock, x86: Add para-virtualization support
...0x20 [<ffffffff8121a7fa>] sysfs_kf_seq_show+0xca/0x1b0 [<ffffffff81218a13>] kernfs_seq_show+0x23/0x30 [<ffffffff811c82db>] seq_read+0xbb/0x400 [<ffffffff812197e5>] kernfs_fop_read+0x35/0x40 [<ffffffff811a4223>] vfs_read+0xa3/0x110 [<ffffffff811a47e6>] SyS_read+0x56/0xd0 [<ffffffff810f3e16>] ? __audit_syscall_exit+0x216/0x2c0 [<ffffffff815b3ca9>] system_call_fastpath+0x16/0x1b Code: Bad RIP value. RSP <ffff8818b7097db0> CR2: 0000000000000000 ---[ end trace 69d0e259c9ec632f ]--- It seems like call site patching isn't properly...
2014 Nov 26
1
[PATCH v12 09/11] pvqspinlock, x86: Add para-virtualization support
...0x20 [<ffffffff8121a7fa>] sysfs_kf_seq_show+0xca/0x1b0 [<ffffffff81218a13>] kernfs_seq_show+0x23/0x30 [<ffffffff811c82db>] seq_read+0xbb/0x400 [<ffffffff812197e5>] kernfs_fop_read+0x35/0x40 [<ffffffff811a4223>] vfs_read+0xa3/0x110 [<ffffffff811a47e6>] SyS_read+0x56/0xd0 [<ffffffff810f3e16>] ? __audit_syscall_exit+0x216/0x2c0 [<ffffffff815b3ca9>] system_call_fastpath+0x16/0x1b Code: Bad RIP value. RSP <ffff8818b7097db0> CR2: 0000000000000000 ---[ end trace 69d0e259c9ec632f ]--- It seems like call site patching isn't properly...
2006 Oct 01
4
Kernel BUG at arch/x86_64/mm/../../i386/mm/hypervisor.c:197
Hello list, I just got this ominous bug on my machine, that has already been seen several times: http://lists.xensource.com/archives/html/xen-devel/2006-01/msg00180.html The machine is very similar, it''s a machine with two dual-core opterons, running one of the latest xen-3.0.3-unstable (20060926 hypervisor, and a vanilla 2.6.18 + xen patch from Fedora from 20060915). This machine was
2016 Feb 27
2
Hung kernel task on CentOS 7.2, fprintd and libvirtd
...eb 26 12:55:05 badboy kernel: [<ffffffff8125c28b>] ? read+0x6b/0x1f0 > Feb 26 12:55:05 badboy kernel: [<ffffffff8125c2fb>] read+0xdb/0x1f0 > Feb 26 12:55:05 badboy kernel: [<ffffffff811de43c>] vfs_read+0x9c/0x170 > Feb 26 12:55:05 badboy kernel: [<ffffffff811def8f>] SyS_read+0x7f/0xe0 > Feb 26 12:55:05 badboy kernel: [<ffffffff81645909>] system_call_fastpath+0x16/0x1b Since fprintd is the fingerprint reader daemon and this server doesn?t have such a peripheral, I removed the service. Now sudo is fast again. [*] Although that solves my immediate problem, wh...
2017 Dec 06
2
[PATCH] ptr_ring: Add barriers to fix NULL-pointer exception
...0] [<ffff000008812f24>] tun_do_read.part.9+0x20c/0x4f0 [35322.720149] [<ffff0000088133f0>] tun_chr_read_iter+0xc0/0xe0 [35322.731638] [<ffff000008288f80>] __vfs_read+0x100/0x160 [35322.742249] [<ffff00000828a224>] vfs_read+0x8c/0x148 [35322.752344] [<ffff00000828b464>] SyS_read+0x6c/0xd8 [35322.762263] [<ffff0000080833f0>] el0_svc_naked+0x24/0x28 [35322.773042] Code: d503201f f9400e93 b940e280 91051274 (f9403261) Reported-by: Joseph DeVincentis <Joseph.DeVincentis at cavium.com> Signed-off-by: George Cherian <george.cherian at cavium.com> --- include/l...
2017 Dec 06
2
[PATCH] ptr_ring: Add barriers to fix NULL-pointer exception
...0] [<ffff000008812f24>] tun_do_read.part.9+0x20c/0x4f0 [35322.720149] [<ffff0000088133f0>] tun_chr_read_iter+0xc0/0xe0 [35322.731638] [<ffff000008288f80>] __vfs_read+0x100/0x160 [35322.742249] [<ffff00000828a224>] vfs_read+0x8c/0x148 [35322.752344] [<ffff00000828b464>] SyS_read+0x6c/0xd8 [35322.762263] [<ffff0000080833f0>] el0_svc_naked+0x24/0x28 [35322.773042] Code: d503201f f9400e93 b940e280 91051274 (f9403261) Reported-by: Joseph DeVincentis <Joseph.DeVincentis at cavium.com> Signed-off-by: George Cherian <george.cherian at cavium.com> --- include/l...