From owner-freebsd-current@FreeBSD.ORG Tue Jul 13 21:05:11 2004 Return-Path: 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 0665116A4CE; Tue, 13 Jul 2004 21:05:11 +0000 (GMT) Received: from mailout1.informatik.tu-muenchen.de (mailout1.informatik.tu-muenchen.de [131.159.0.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32D0E43D3F; Tue, 13 Jul 2004 21:05:10 +0000 (GMT) (envelope-from langd@informatik.tu-muenchen.de) Date: Tue, 13 Jul 2004 23:05:08 +0200 From: Daniel Lang To: Robert Watson Message-ID: <20040713210508.GA893@atrbg11.informatik.tu-muenchen.de> References: <20040711100553.GA64553@atrbg11.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Geek: GCS/CC d-- s: a- C++$ UBS++++$ P+++$ L- E-(---) W+++(--) N++ o K w--- O? M? V? PS+(++) PE--(+) Y+ PGP+ t++ 5+++ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r+++ y+ User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at informatik.tu-muenchen.de cc: Don Lewis cc: ps@FreeBSD.org cc: current@FreeBSD.org Subject: Re: panic: m_copym, length > size of mbuf chain X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 13 Jul 2004 21:05:11 -0000 Hi Robert, Robert Watson wrote on Tue, Jul 13, 2004 at 03:42:09PM -0400: [..] > Is it possible to get the box running with SACK again for debugging > purposes? Resolving this issue would be a very good thing. Thanks! [..] Well.... I am really hesitant about this matter. The box used to be (at least from my perspective) one of the top 5 mirror hosts in Germany for more than a dozen public domain projects, like FreeBSD, other BSDs, Apache, Postgres, a couple of Linux distros and many more. All in all this box has 100-200 mirrors running (well if they are running). So at the moment, I am really glad to have the thing up again. However, somebody of the SACK development team has contacted me, to obtain access to the crashdump and I am happy to provide this access. Maybe this is already sufficient to resolve the problem. So, I will provide access to this data, and we will see if these people can find the problem. If not, well, I am still open to suggestions. It all depends, I'd say. I am very glad and thank everybody who helped to solve my problem, and I am still willing to contribute my share. One of the major obstacles is, that I am (actually starting from today) no longer an employee at the Technische Universitaet Muenchen, the university running the LEO project (where the machine is hosted). So I for the sake of the transition, I have had a strong interest in leaving a stable service to be hosted by my collegues and successors. The instability problem in the last weeks has caused a really really bad headache. So if things are settled down and there is someone who has equal competencies in running the LEO services, I am confident more thorough debugging assitancy can be provided. To make things clear, I volunteered to assist the LEO project in the future, but I cannot promise anything right now, so I would like to keep the impact to the production service as minimal as possible. Thanks and best regards, Daniel -- IRCnet: Mr-Spock - Burn them to ashes, then burn the ashes. - Daniel Lang * dl@leo.org * +49 89 289 18532 * http://www.leo.org/~dl/