On Wed, 12 Sep 2007, Kris Kennaway wrote: > Mario Sergio Fujikawa Ferreira wrote: >> I had 3 panics today. All seem to be related to ipf code. I have >> disabled ipf for the time being. >> >> I am attaching the kgdb backtraces. I am saving the cores. Let me know >> if there is anything I can do to help. >> >> FreeBSD exxodus.home.home 7.0-CURRENT FreeBSD 7.0-CURRENT #2: Mon Sep 10 >> 15:01:49 BRT 2007 root_at_exxodus.home.home:/usr/obj/usr/src/sys/LIOUX i386 >> >> -current as of Sep 10 2007. > > Yes, known issue. The lack of response by the ipf maintainer so far > suggests it probably will not be fixed in 7.0. This should be documented in > the relnotes. The quick, and probably correct, fix is to replace all use of sx(9) with rw(9) in ipf. There might be places where a copying/copyout is being performed with the lock held, in which case this will trigger new warnings. Robert N M Watson Computer Laboratory University of CambridgeReceived on Wed Sep 12 2007 - 09:47:59 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:17 UTC