In article <20160811.153708.78150616.ja...@uninett.no>, Jarle Greipsland <ja...@uninett.no> wrote: >[ Followups to port-i386, please ] >I wrote[1]: >> 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 >> ja...@singsaker.uninett.no:/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? >
Please try compiling ufs_lookup.c with -O0... christos