Date: Thu, 8 Aug 2002 11:01:44 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Peter Grehan <peterg@ptree32.com.au> Cc: freebsd-ppc@freebsd.org Subject: Re: updated kernels Message-ID: <15698.34776.880061.81032@grasshopper.cs.duke.edu> In-Reply-To: <3D528052.B7220749@ptree32.com.au> References: <3D528052.B7220749@ptree32.com.au>
index | next in thread | previous in thread | raw e-mail
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 messagehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15698.34776.880061.81032>