[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Mangled file system directory panic
On Thu, Aug 11, 2016 at 03:37:08PM +0200, Jarle Greipsland wrote:
> [ Followups to port-i386, please ]
> I wrote:
> > I have a system where I can almost deterministally provoke a
> > kernel panic by doing a 'tar -zxpf comp.tgz'.
> > The panic messages reported by crash is something like:
> > System panicked: /mnt: bad dir ino 42369 at offset 560: NUL in name  i=0, namlen=4
> [ ... ]
> > NetBSD 7.99.34 (DARLING) #1: Sat Jul 30 20:01:15 CEST 2016
> > jarle%singsaker.uninett.no@localhost:/usr/obj/sys/arch/i386/compile/DARLING
> > total memory = 127 MB
> > avail memory = 120 MB
> > timecounter: Timecounters tick every 10.000 msec
> > timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
> > Generic PC
> > mainbus0 (root)
> > cpu0 at mainbus0
> > cpu0: Intel 486-class
> > eisa0 at mainbus0
> > isa0 at mainbus0
> [ ... ]
> I have since managed to pin-point where things started to go
> wrong -- CVS commit-wise. A -current kernel from CVS with tag
> '2016.04.03.03.00.00' works just fine, while a kernel with tag
> '2016.04.03.07.00.00' panics. The only significant commit in
> that interval is a change of compiler for the i386 port to GCC
> 5.3 (http://mail-index.netbsd.org/source-changes/2016/04/03/msg073782.html).
> Are there known bugs in our compiler for (plain) i486 systems?
> : http://mail-index.netbsd.org/current-users/2016/07/30/msg029876.html
> You are in a dark room with a compiler, emacs, an internet connection,
> and a thermos of coffee.
> Your move ? -- David A. Honig
Is that PR/51094?
Main Index |
Thread Index |