This panic started happening to me after I cvsup'd and rebuilt yesterday. Prior to that I never had the problem with a -CURRENT from 04/26 (using the same steps listed below). Now I can reliably reproduce the crash on: FreeBSD bulgogi.cisco.com 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Fri May 2 14:08:06 EDT 2003 marcus_at_bulgogi.cisco.com:/usr/obj/usr/src/sys/BULGOGI i386 All my file systems are UFS2 with softupdates. The way I reproduce this, is I have the following: /dev/ad0s1f 34G 3.0G 28G 10% /space On /space, I have a current ports tree in ports/. I have /space NFS-exported with /space/ports as an allowed mount point. I then mount /space/ports to /space/jails/current/a/ports on the same machine: mount -o nfsv3,intr -r localhost:/space/ports /space/jails/current/a/ports Then, I run: chroot /space/jails/current (cd /usr/ports/x11/gnome2; make checksum-recursive) A few seconds later, the system crashes with the same backtrace that has previously been sent to the list. Running a full fsck from single-user did not help. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:06 UTC