co...@sdf.org writes: > On Thu, Aug 11, 2016 at 03:37:08PM +0200, Jarle Greipsland 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 [ ... ] >> 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? [ ... ]
> Is that PR/51094? It certainly looks closely related, symptom-wise. I have tried the suggested workaround, but the kernel still panics. -jarle