From owner-freebsd-stable@FreeBSD.ORG Tue Aug 1 07:40:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F148316A4DF for ; Tue, 1 Aug 2006 07:40:36 +0000 (UTC) (envelope-from m.ehinger@ltur.de) Received: from postx.gateway-inter.net (postx.gateway-inter.net [213.144.19.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7532B43D49 for ; Tue, 1 Aug 2006 07:40:36 +0000 (GMT) (envelope-from m.ehinger@ltur.de) To: freebsd-stable@freebsd.org From: m.ehinger@ltur.de MIME-Version: 1.0 Message-ID: Date: Tue, 1 Aug 2006 09:40:30 +0200 Content-type: text/plain; charset=US-ASCII Cc: eric.j.christeson@gmail.com Subject: ncplogin panic 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: Tue, 01 Aug 2006 07:40:37 -0000 Hi, i had the same problem. See my thread on the freebsd-fs mailinglist http://lists.freebsd.org/pipermail/freebsd-fs/2006-July/002060.html After some research i use the attached patch against ncp_sock.c. So it is not the real solution to this problem it only avoids the panics. I'm using it quiet a while without any other known problems. Hopefully someone with more knowledge can help on this. I also get some "md_get_mem(461): incomplete copy" messages which seem to do no harm, so far. Regards, Maik !!! Use atyour own risk !!! --- ncp_sock.c.orig Fri Jan 7 02:45:49 2005 +++ ncp_sock.c Thu Jul 20 14:12:45 2006 @@ -189,7 +189,12 @@ struct thread *td = curthread; struct ucred *cred = NULL; - return so->so_proto->pr_usrreqs->pru_sopoll(so, events, cred, td); + if ( td->td_selq.tqh_last == NULL ) { + printf("ncp_poll: td->td_selq.tqh_last == NULL\n"); + return 0; + } + + return so->so_proto->pr_usrreqs->pru_sopoll(so, events, cred, td); } int ---- pach ends here ---