From owner-freebsd-ppc Thu Aug 8 8: 3:48 2002 Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 891A937B401 for ; Thu, 8 Aug 2002 08:03:39 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF06E43E81 for ; Thu, 8 Aug 2002 08:02:16 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA23259; Thu, 8 Aug 2002 11:02:15 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g78F1ig03387; Thu, 8 Aug 2002 11:01:44 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15698.34776.880061.81032@grasshopper.cs.duke.edu> Date: Thu, 8 Aug 2002 11:01:44 -0400 (EDT) To: Peter Grehan Cc: freebsd-ppc@freebsd.org Subject: Re: updated kernels In-Reply-To: <3D528052.B7220749@ptree32.com.au> References: <3D528052.B7220749@ptree32.com.au> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-ppc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Grehan writes: > I've put two new kernels up. This may help those who've had > the mysterious crashes at boot, since I suspect that is related > to having > 256Mb of RAM. The fix clamps the amount of > used memory to 256Mb max. This limitation will be removed when > things have settled down a bit. > > The other fixes are: > - raw i/o should work (dd) > - the secondary ATA channel should be enabled (untested) > > The NFS small text file bug is still being worked on :-( Cool.. I think I've got a few more for you too, none new ;) I found that doing heavy NFS read traffic will cause my g4 to lock up. But I think that its any heavy network traffic at all -- a flood ping will show problems: # /sbin/ping -f 10.0.0.2 PING 10.0.0.2 (10.0.0.2): 56 data bytes ..........................................................................................^C Appears like machine is hung, but it could just be that the nic has gone insane.. (it will print things on the console and take input on console for a few seconds after pings stop getting through). The sysctl problem is still present: % sysctl -a >& /dev/null panic: kmem_malloc: entr Does ddb work on ppc yet? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ppc" in the body of the message