Date: Sat, 21 Oct 2000 10:09:54 +0200 (SAT) From: John Hay <jhay@icomtek.csir.co.za> To: matusita@jp.FreeBSD.org (Makoto MATSUSHITA) Cc: current@FreeBSD.ORG Subject: Re: current.freebsd.org problems? Message-ID: <200010210809.e9L89sk93221@zibbi.icomtek.csir.co.za> In-Reply-To: <20001020181137T.matusita@jp.FreeBSD.org> from Makoto MATSUSHITA at "Oct 20, 2000 06:11:37 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > jhay> For now I just went back to an older kernel that works for me. > > Would you please explain "an older kernel" ? I'm using a kernel as of > Sep/30/2000 and it panics. > > *** > > Note that this (Sep/30/2000) kernel doesn't panic until Oct/13/2000. > Between Oct/14/2000 and Oct/17/2000, "make release" was failed at > buildworld. Oct/18/2000, panic. Oct/19/2000, also panic. > It looks like I spoke too soon. My 2000-10-05 kernel that previously worked also now panics. It must be somewhere when the floppies are made. On the serial console I see: Oct 21 04:44:49 beast /boot/kernel/kernel: /mnt: optimization changed from SPACE to TIME /mnt: bad dir ino 2 at offset 0: mangled entry panic: ufs_dirbad: bad dir cpuid = 0; lapic.id = 01000000 boot() called on cpu#0 Does the mangled entry on /mnt mean there is something wrong in the /mnt filesystem? That would be the floppy image. Also it does not reboot after the panic. It just get stuck after printing a lot of "microuptime() went backwards (28431.4508250 -> 28431.2820885)" messages. John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200010210809.e9L89sk93221>