Date: Sat, 1 Mar 1997 12:50:53 +0900 (JST) From: Michael Hancock <michaelh@cet.co.jp> To: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com> Cc: FreeBSD Hackers <Hackers@FreeBSD.ORG> Subject: Re: Another installment of the "dup alloc"/"bad dir" panic problems. Message-ID: <Pine.SV4.3.95.970301124630.15992B-100000@parkplace.cet.co.jp> In-Reply-To: <199703010101.UAA05470@lakes.water.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 28 Feb 1997, Thomas David Rivers wrote: > > > It now appears that having the printf()s in disksort() affects the problem > > > in a positive manner (that is, I'm not able to demonstrate the previous > > > "non-writing" behaviour I had seen; the inode in question is reliably > > > filled with zeros.) The old "printf's makes the problem go away effect". I hate when that happens. ;-) Can you do a gcc -v and show us the flags you use to compile the kernel? If missed these, in case you've already posted them. Regards, Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SV4.3.95.970301124630.15992B-100000>