Date: Mon, 9 Jun 2008 21:17:54 +0200 From: Hans Petter Selasky <hselasky@c2i.net> To: ticso@cicely.de Cc: Perforce Change Reviews <perforce@freebsd.org> Subject: Re: PERFORCE change 143121 for review Message-ID: <200806092117.55412.hselasky@c2i.net> In-Reply-To: <20080609032050.GR71712@cicely7.cicely.de> References: <200806081504.m58F4CtW034713@repoman.freebsd.org> <200806082313.03865.hselasky@c2i.net> <20080609032050.GR71712@cicely7.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Bernd, When I re-enabled: options PSEUDOFS in my kernel configuration file, everything worked again! --HPS On Monday 09 June 2008, Bernd Walter wrote: > On Sun, Jun 08, 2008 at 11:13:03PM +0200, Hans Petter Selasky wrote: > > Hi, > > > > It might look like that my "init" executable in the file system is out of > > date. The kernel boots fine up to the following point: > > > > Trying to mount root from ufs:/dev/md0 > > warning: no time-of-day clock registered, system time will not be set > > accurately > > Jun 4 20:32:47 init: login_getclass: unknown class 'daemon' > > Fatal kernel mode data abort: 'Alignment Fault 3' > > trapframe: 0xc67f7a24 > > We've seen this at least on RM9200 from time to time - not sure about > other arm. > Try adding or removing a driver to your kernel and see if it helps. > It's some kind of heisenbug, because a small unrelated change and the > problem is away, which makes is hard to debug. > See arm@ mail archives for more details. > IIRC it happened earlier during boot, so this can still be something > different after all. > Even with an out of date init the kernel shouldn't panic with an > alignment fault.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200806092117.55412.hselasky>