From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 21:40:11 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5697F16A41F; Tue, 1 Nov 2005 21:40:11 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from indor.net.tomline.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7F5C43D73; Tue, 1 Nov 2005 21:40:02 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000027143.msg; Wed, 02 Nov 2005 03:39:56 +0600 X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 87696, updated: 31.10.2005] To: John Baldwin References: <200511011030.06028.jhb@freebsd.org> From: Victor Snezhko Date: Wed, 02 Nov 2005 03:39:53 +0600 In-Reply-To: <200511011030.06028.jhb@freebsd.org> (John Baldwin's message of "Tue, 1 Nov 2005 10:30:05 -0500") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Wed, 02 Nov 2005 03:39:56 +0600 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru X-VVS-Spam: false Cc: freebsd-current@freebsd.org Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 21:40:11 -0000 John Baldwin writes: >> > > > OK, here it is. It's happened between 2005.10.21.19.42.50 and >> > > > 2005.10.22.05.07.00. >> > > > Since then, panic is absolutely reproducible. >> > > >> > > Actually, when I took INET6 from kernel (once again, it's GENERIC) >> > > these panics stop. >> > >> > Hmmm. Are those timestamps UTC? If so, there's nothing worthwhile that >> > changed in there: >> >> I experience the same problem, just wanted to report - when I >> cvsupped to the kernel as of 2005.10.21.19.42.50, problem remained. >> >> nooption INET6 actually helps. > > What about 2005.10.21.16.00.00? Does that fail or break? No, that doesn't trap. So, we found a narrow timeslice at which things broken. -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru