From owner-freebsd-stable@FreeBSD.ORG Mon Oct 26 14:09:09 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55A1B106566C for ; Mon, 26 Oct 2009 14:09:09 +0000 (UTC) (envelope-from jbozza@mindsites.com) Received: from mail.thinkburst.com (mail.thinkburst.com [204.49.104.46]) by mx1.freebsd.org (Postfix) with ESMTP id 2523B8FC18 for ; Mon, 26 Oct 2009 14:09:08 +0000 (UTC) Received: from mailgate.mindsites.net (gateway.mindsites.net [204.49.104.36]) by mail.thinkburst.com (Postfix) with ESMTP id 9C1D81CC27; Mon, 26 Oct 2009 09:09:08 -0500 (CDT) Received: from remote.mindsites.com (unknown [10.1.1.5]) by mailgate.mindsites.net (Postfix) with ESMTP id 7A01317049; Mon, 26 Oct 2009 09:09:08 -0500 (CDT) Received: from ATLAS.msg.local ([fe80::48f5:88b0:6093:4f67]) by ATLAS.msg.local ([fe80::48f5:88b0:6093:4f67%10]) with mapi; Mon, 26 Oct 2009 09:09:08 -0500 From: Jaime Bozza To: Kostik Belousov , Dylan Cochran Date: Mon, 26 Oct 2009 09:09:06 -0500 Thread-Topic: Possible scheduler (SCHED_ULE) bug? Thread-Index: AcpUJsMCkKSZ+UzjTTawJE5X5gOI6gCHqoww Message-ID: References: <20091023212104.GH2160@deviant.kiev.zoral.com.ua> In-Reply-To: <20091023212104.GH2160@deviant.kiev.zoral.com.ua> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-stable@freebsd.org" Subject: RE: Possible scheduler (SCHED_ULE) bug? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Oct 2009 14:09:09 -0000 From: Kostik Belousov [mailto:kostikbel@gmail.com] > Can you look up the source line for kern_sendfile+0x90d in your > kernel ? Do kgdb kernel.debug, then execute "list *(kern_sendfile+0x90d)"= . In my case, it was kern_sendfile+0x6ad (rebuilt with RELENG_7 this weekend)= . Here's the output: (kgdb) list *(kern_sendfile+0x6ad) 0xc0855fdd is in kern_sendfile (atomic.h:160). 155 static __inline int 156 atomic_cmpset_int(volatile u_int *dst, u_int exp, u_int src) 157 { 158 u_char res; 159 160 __asm __volatile( 161 " " MPLOCKED " " 162 " cmpxchgl %2,%1 ; " 163 " sete %0 ; " 164 "1: " Not much to go on there. I posted a backtrace in a previous email, but the= relevant sections (I think) are: #14 0xc0855fdd in kern_sendfile (td=3D0xc771db40, uap=3D0xc72e2cfc, hdr_uio= =3D0x0, trl_uio=3D0x0, compat=3D0) at atomic.h:160 #15 0xc0856d31 in do_sendfile (td=3D0xc771db40, uap=3D0xc72e2cfc, compat=3D= 0) at /usr/src/sys/kern/uipc_syscalls.c:1775 #16 0xc0856dd3 in sendfile (td=3D0xc771db40, uap=3D0xc72e2cfc) at /usr/src/= sys/kern/uipc_syscalls.c:1746 #17 0xc0b01365 in syscall (frame=3D0xc72e2d38) at /usr/src/sys/i386/i386/tr= ap.c:1094 #18 0xc0ae5960 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s= :262 #19 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) I'm still going to test the specific boundary, but if there's more informat= ion I can give, let me know! Jaime