From owner-freebsd-questions Thu Jul 29 14:33:12 1999 Delivered-To: freebsd-questions@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 9026F1560F for ; Thu, 29 Jul 1999 14:32:22 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id RAA11390; Thu, 29 Jul 1999 17:30:21 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id RAA10897; Thu, 29 Jul 1999 17:30:20 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id RAA74651; Thu, 29 Jul 1999 17:30:19 -0400 (EDT) Date: Thu, 29 Jul 1999 17:30:19 -0400 (EDT) From: Thomas David Rivers Message-Id: <199907292130.RAA74651@lakes.dignus.com> To: jonc@pinnacle.co.nz, rivers@dignus.com Subject: Re: 3.2R Console hanging. Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Thu, 29 Jul 1999, Thomas David Rivers wrote: > > > > Was your laptop connected to a network? One thing I have just recalled > > > was that that the console hung usually shortly after sending the > > > work-packet back over the 'Net via ppp. Some weird interference with > > > the network code (unlikely as it sounds)? > > > > Well - yes - it is connected to a network. It's an internal network > > with a separate gateway to the outside world. > > Would you care to try disconnecting it from your network and try it? > > At the very least this will eliminate the possibility that it could be > the networking code. At best it will give us somewhere to point the > problem at. > You mean, after it's gotten a packet of work to chug on? Sure... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message