At Tue, 9 Dec 2003 19:41:11 -0800 (PST), Don Lewis wrote: > I ran into this problem in 5.2-CURRENT. It has sinced been fixed there, > in sys/vm/mmap.c 1.175. I believe this is under consideration for > mergeing into RELENG_5_2. In the mean time, you can get under way again > by setting vfs_badlock_panic and vfs_badlock_print to 0 in the ddb and > continuing. This panic will also go away if you rebuild your kernel > with vnode lock checking disabled. Thanks! I've applied the diff between 1.174 (RELENG_5_2) and 1.175 and it works fine. -- Jun Kuriyama <kuriyama_at_imgsrc.co.jp> // IMG SRC, Inc. <kuriyama_at_FreeBSD.org> // FreeBSD ProjectReceived on Tue Dec 09 2003 - 20:32:21 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:33 UTC