From owner-freebsd-current@FreeBSD.ORG Fri Jul 22 00:40:37 2005 Return-Path: X-Original-To: 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 364E416A44C; Fri, 22 Jul 2005 00:40:37 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F85643E1D; Fri, 22 Jul 2005 00:39:56 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id B6F7846B06; Thu, 21 Jul 2005 20:39:35 -0400 (EDT) Date: Fri, 22 Jul 2005 01:40:07 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Andrey Chernov In-Reply-To: <20050722003657.GA1415@nagual.pp.ru> Message-ID: <20050722013938.H16902@fledge.watson.org> References: <20050721134816.GA8550@nagual.pp.ru> <20050721142445.GA77847@stack.nl> <20050721143443.GB10010@nagual.pp.ru> <20050721.091844.10574798.imp@bsdimp.com> <20050721152946.GA11578@nagual.pp.ru> <20050722011804.O16902@fledge.watson.org> <20050722003657.GA1415@nagual.pp.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: marcolz@stack.nl, wpaul@windriver.com, current@FreeBSD.ORG, "M. Warner Losh" Subject: Re: rl(4) is not ready for mpsafenet net enough? (silent reboots) 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: Fri, 22 Jul 2005 00:40:37 -0000 On Fri, 22 Jul 2005, Andrey Chernov wrote: > On Fri, Jul 22, 2005 at 01:20:46AM +0100, Robert Watson wrote: >> FYI, most locking bugs in network interfaces that I've seen don't result >> in a spontaneous reboot, and that's a somewhat worrying symptom. Is this >> something you can easily reproduce in a short period of time, or in >> particular, using a particular program or system call? Is there any >> chance your box has firewire and you can use a firewire debugger to >> inspect memory? > > I can't reproduce it, it happens after few hours running. Perhaps the > problem is not in rl(4) and making it GIANT only mask the problem. I > have spare hardware to swith to and experiment and I'll see what > happens. If the same problem occurs using a different adapter but identical software configuration otherwise, that would be very helpful to know. Robert N M Watson