search for: tracesys

...;ffffffff882680af>] :xfs:xfs_access+0x3d/0x46 [2870477.695899]? [<ffffffff80264929>] _spin_lock_irqsave+0x9/0x14 [2870477.695923]? [<ffffffff802df4a3>] vfs_mkdir+0xe3/0x152 [2870477.695933]? [<ffffffff802dfa79>] sys_mkdirat+0xa3/0xe4 [2870477.695953]? [<ffffffff80260295>] tracesys+0x47/0xb6 [2870477.695963]? [<ffffffff802602f9>] tracesys+0xab/0xb6 [2870477.695977] [2870477.695985] xfs_force_shutdown(sda5,0x8) called from line 1139 of file fs/xfs/xfs_trans.c.? Return address = 0xffffffff88262c46 [2870477.696452] Filesystem "sda5": Corruption of in-memory data...

...ea (ffffffff885d9000) Oct 13 09:27:46 new kernel: WARNING: at mm/vmalloc.c:329 __vunmap() Oct 13 09:27:46 new kernel: Oct 13 09:27:46 new kernel: Call Trace: Oct 13 09:27:46 new kernel: [<ffffffff800a8b6b>] sys_delete_module+0x1b3/0x1d4 Oct 13 09:27:46 new kernel: [<ffffffff8005d28d>] tracesys+0xd5/0xe0 Oct 13 09:27:46 new kernel: -------------------------------------------------------------------------------------------- Followed by (a few times) -------------------------------------------------------------------------------------------- Oct 13 09:27:46 new kernel: WARNING: at mm/vma...

...lookup+0x275/0x2f1 [<ffffffff80012851>] getname+0x15b/0x1c2 [<ffffffff800239d1>] __user_walk_fd+0x37/0x4c [<ffffffff80028905>] vfs_stat_fd+0x1b/0x4a [<ffffffff80039fa2>] fcntl_setlk+0x243/0x273 [<ffffffff80023703>] sys_newstat+0x19/0x31 [<ffffffff8005d229>] tracesys+0x71/0xe0 [<ffffffff8005d28d>] tracesys+0xd5/0xe0 Code: 00 00 00 00 00 00 00 00 70 4d 4f 9d 00 81 ff ff 98 e4 4b dc RIP [<ffff8100dc435cf0>] RSP <ffff81001529fd18> CR2: ffff8100dc435cf0 <0>Kernel panic - not syncing: Fatal exception This suggests that something happe...

...irectly from this functionWARNING: at security/security.c:51 security_ops_task_setrlimit() Call Trace: [<ffffffff8012ee59>] security_ops_task_setrlimit+0x87/0x96 [<ffffffff8009dbc9>] do_prlimit+0xd7/0x1d2 [<ffffffff8009ed12>] sys_setrlimit+0x36/0x43 [<ffffffff8005d29e>] tracesys+0xd5/0xdf -- Eero

...+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

...ENOSYS return call from the syscall; what actually happens (only in the 64-bit kernel) is that you get back the system call number. The 32-bit kernel does not suffer from this bug, and the pv-ops implementation in the upstream Linux kernel also does not have this bug. The attached patch makes the tracesys path look the same as it does in upstream Linux, and ensures that we return -ENOSYS on this path. Signed-off-by: Chris Lalancette <clalance@redhat.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...03 [<ffffffff8002f96a>] __writeback_single_inode+0x1dd/0x31c [<ffffffff800f7454>] sync_inode+0x24/0x33 [<ffffffff8804c37e>] :ext3:ext3_sync_file+0xce/0xf8 [<ffffffff8004fe60>] do_fsync+0x52/0xa4 [<ffffffff800e48c9>] __do_fsync+0x23/0x36 [<ffffffff8005d28d>] tracesys+0xd5/0xe0 INFO: task VBoxHeadless:20743 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. VBoxHeadless D ffffffff801563dc 0 20743 1 20742 (NOTLB) ffff8107717ebd98 0000000000000086 0000000c717ebd18 0000...

...ffffffff8831b1f9>] :ip_conntrack:destroy_conntrack+0x107/0x112 [<ffffffff8831a18e>] :ip_conntrack:ip_ct_iterate_cleanup+0x3e/0x124 [<ffffffff8831a2ea>] :ip_conntrack:ip_conntrack_cleanup+0x68/0xc5 [<ffffffff802a2c55>] sys_delete_module+0x196/0x1c5 [<ffffffff8025c29c>] tracesys+0xdc/0xf0 [<0000003864ecd817>] Code: 48 8b 40 50 48 85 c0 74 05 48 89 df ff d0 0f 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 ke...

...47:55 vmail kernel: [<ffffffff80063cad>] .text.lock.mutex+0xf/0x14 May 2 21:47:55 vmail kernel: [<ffffffff80013ed6>] generic_file_llseek+0x2a/0x8b May 2 21:47:55 vmail kernel: [<ffffffff8002563b>] sys_lseek+0x40/0x60 May 2 21:47:58 vmail kernel: [<ffffffff8005d229>] tracesys+0x71/0xe0 May 2 21:47:58 vmail kernel: [<ffffffff8005d28d>] tracesys+0xd5/0xe0 May 2 21:47:58 vmail kernel: May 2 22:42:53 vmail nrpe[29199]: Could not read request from client, bailing out... May 2 22:42:53 vmail nrpe[29199]: INFO: SSL Socket Shutdown. May 2 22:42:53 vmail nrpe[29201]...

...x2e Mar 30 12:26:39 jgs kernel: [<ffffffff810a0201>] lookup_one_len_kern+0x73/0xf2 Mar 30 12:26:39 jgs kernel: [<ffffffff81098087>] vfs_read+0xcb/0x173 Mar 30 12:26:39 jgs kernel: [<ffffffff8109854f>] sys_pread64+0x50/0x70 Mar 30 12:26:39 jgs kernel: [<ffffffff8100bcd1>] tracesys+0x71/0xda Mar 30 12:26:39 jgs kernel: [<ffffffff8100bd35>] tracesys+0xd5/0xda Mar 30 12:26:39 jgs kernel: Mar 30 12:26:39 jgs kernel: Mar 30 12:26:39 jgs kernel: Code: 48 8b 44 c7 50 4c 8d 44 08 42 41 8a 10 ff c2 41 88 10 8a 40 Mar 30 12:26:39 jgs kernel: RIP [<ffffffff81079004>] __in...

...:20:01 localhost kernel: [<ffffffff800161d8>] vfs_write+0xce/0x174 Jan 8 05:20:01 localhost kernel: [<ffffffff80016a8d>] sys_write+0x2d/0x6e Jan 8 05:20:01 localhost kernel: [<ffffffff80016aa5>] sys_write+0x45/0x6e Jan 8 05:20:01 localhost kernel: [<ffffffff8005b28d>] tracesys+0xd5/0xe0 Jan 8 05:20:01 localhost kernel: Jan 8 05:20:01 localhost kernel: handlers: Jan 8 05:20:01 localhost kernel: [<ffffffff801dadc4>] (usb_hcd_irq+0x0/0x55) Jan 8 05:20:01 localhost kernel: Disabling IRQ #169

...>] ? nouveau_drm_ioctl+0x76/0xa0 [nouveau] [ 2643.920749] [<ffffffff811799b7>] ? do_vfs_ioctl+0x2c7/0x490 [ 2643.920753] [<ffffffff810a25c5>] ? vtime_account_user+0x45/0x60 [ 2643.920757] [<ffffffff81179c19>] ? SyS_ioctl+0x99/0xb0 [ 2643.920761] [<ffffffff818b6dec>] ? tracesys+0x7e/0xe2 [ 2643.920765] [<ffffffff818b6e4b>] ? tracesys+0xdd/0xe2 [ 2643.920768] Code: 6c 24 38 48 89 fb 4c 89 64 24 40 4c 89 6c 24 48 41 89 d4 4c 89 74 24 50 4c 89 7c 24 58 48 89 f5 48 8b 07 49 89 e1 be 01 00 00 00 <48> 8b 50 08 48 8b 8a f0 00 00 00 4c 8b aa 50 07 00 00 48 8b 41 [ 2...

...:ptlrpc:ldlm_flock_completion_ast+0x0/0x690 Jan 31 10:45:24 opteron-ren-11 kernel: [<ffffffff802ac2ff>] audit_syscall_entry+0x141/0x174 Jan 31 10:45:24 opteron-ren-11 kernel: [<ffffffff802d39d6>] sys_flock+0x117/0x150 Jan 31 10:45:24 opteron-ren-11 kernel: [<ffffffff8025729c>] tracesys+0xdc/0xe1 Jan 31 10:45:24 opteron-ren-11 kernel: Jan 31 10:45:24 opteron-ren-11 kernel: LustreError: dumping log to /tmp/lustre-log.1201772724.24836 I attached the lustre-log. What could cause this problem? The reason, I wanted to use flock is there are some softwares, which cannot save files b...

...9 backup kernel: [<ffffffff80022861>] clear_inode+0xd2/0x123 Sep 7 21:08:19 backup kernel: [<ffffffff8002f19a>] generic_delete_inode+0xde/0x143 Sep 7 21:08:19 backup kernel: [<ffffffff8003c1f6>] do_unlinkat+0xd5/0x141 Sep 7 21:08:19 backup kernel: [<ffffffff8005d229>] tracesys+0x71/0xe0 Sep 7 21:08:19 backup kernel: [<ffffffff8005d28d>] tracesys+0xd5/0xe0 Sep 7 21:08:19 backup kernel: Sep 7 21:08:19 backup kernel: xfs_force_shutdown(sdb1,0x8) called from line 4267 of file /home/buildsvn/rpmbuild/BUILD/xfs-kmod-0.4/_kmod_build_/xfs_bmap.c. Return address = 0xff...

...fffff810ad804>] ? load_module+0x18d3/0x1b9a [ 71.125060] [<ffffffff810ab117>] ? mod_kobject_put+0x42/0x42 [ 71.125060] [<ffffffff81118716>] ? vfs_read+0xf7/0x13e [ 71.125060] [<ffffffff810adbad>] ? SyS_finit_module+0x4e/0x62 [ 71.125060] [<ffffffff81420c8f>] ? tracesys+0xe1/0xe6 [ 71.125060] Code: 83 c4 18 5b 5d 41 5c 41 5d c3 8b 47 08 0f b7 57 02 83 e0 fe c1 e2 04 89 c1 83 c9 01 83 c2 0c 85 f6 0f 45 c1 48 63 d2 48 03 57 28 <89> 02 c3 48 8b 46 10 48 83 ef 48 48 85 c0 74 02 ff e0 48 c7 c0 [ 71.125060] RIP [<ffffffff8121ea05>] __msix_mask_irq...

...e_pages+0xe/0x40 Aug 20 10:05:43 server211 kernel: [82025.282040] [<ffffffff811e297a>] ? copy_mount_options+0x3a/0x180 Aug 20 10:05:43 server211 kernel: [82025.282043] [<ffffffff811e3920>] SyS_mount+0x90/0xe0 Aug 20 10:05:43 server211 kernel: [82025.282048] [<ffffffff81760fbf>] tracesys+0xe1/0xe6 Aug 20 10:06:01 server211 CRON[803]: (root) CMD ( /opt/bin/tomcat_check.sh) ------------------------------------------------------------------------------------------------------------------------------------- ???????????????????????????????????????? ?????????????????????????????????...

...e_pages+0xe/0x40 Aug 20 10:05:43 server211 kernel: [82025.282040] [<ffffffff811e297a>] ? copy_mount_options+0x3a/0x180 Aug 20 10:05:43 server211 kernel: [82025.282043] [<ffffffff811e3920>] SyS_mount+0x90/0xe0 Aug 20 10:05:43 server211 kernel: [82025.282048] [<ffffffff81760fbf>] tracesys+0xe1/0xe6 Aug 20 10:06:01 server211 CRON[803]: (root) CMD ( /opt/bin/tomcat_check.sh) ------------------------------------------------------------------------------------------------------------------------------------- ???????????????????????????????????????? ?????????????????????????????????...

...y_change+0x145/0x2f3 [<ffffffff802d17af>] do_truncate+0x5e/0x79 [<ffffffff80212f1a>] may_open+0x1d3/0x22f [<ffffffff8021b4ce>] open_namei+0x2c8/0x6ed [<ffffffff80227a14>] do_filp_open+0x1c/0x38 [<ffffffff8021a1b8>] do_sys_open+0x44/0xbe [<ffffffff802602f9>] tracesys+0xab/0xb6 Code: ff 42 08 8b 07 a9 00 00 20 00 75 0a 0f 0b 68 f5 97 03 88 c2 RIP [<ffffffff88037cb0>] :jbd:journal_grab_journal_head+0x25/0x44 RSP <ffff88001ee5fb50> <0>Kernel panic - not syncing: Fatal exception

...<ffffffff811d088d>] chown_common+0x16d/0x1a0 [376007.682153] [<ffffffff811f2b08>] ? __mnt_want_write+0x58/0x70 [376007.682156] [<ffffffff811d1a8f>] SyS_fchownat+0xbf/0x100 [376007.682159] [<ffffffff811d1aed>] SyS_chown+0x1d/0x20 [376007.682163] [<ffffffff817858bf>] tracesys+0xe1/0xe6 [376007.682165] ---[ end trace 1853311c87a5cd94 ]--- -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

...[<ffffffff80263ac8>] .text.lock.mutex+0xf/0x14 [<ffffffff8021b52d>] open_namei+0xea/0x6d5 [<ffffffff8029cb30>] set_process_cpu_timer+0xc7/0xd2 [<ffffffff80227caa>] do_filp_open+0x1c/0x38 [<ffffffff8021a364>] do_sys_open+0x44/0xbe [<ffffffff802602f9>] tracesys+0xab/0xb6 Monitoring show that in a timeframe of about 3 minutes the load on the systems shot up to over 400 before they died. Since MaxClients is set to 512 I suspect that the processes had a mass-lockup with each process constantly causing a load of 1 (similar to what happens when a process...