From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 00:49:36 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 077D516A419 for ; Wed, 14 Nov 2007 00:49:36 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id 2BF9713C481; Wed, 14 Nov 2007 00:49:34 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <473A4620.8010909@FreeBSD.org> Date: Wed, 14 Nov 2007 01:49:36 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Kip Macy References: <0ECA0F43-497A-4823-8731-D517889D5822@khera.org> <91893E44-B766-4B31-9DA7-62F5EC0CCD45@khera.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Vivek Khera , FreeBSD Stable List Subject: Re: reboot after panic: vm_page_unwire: invalid wire count: 0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2007 00:49:36 -0000 Kip Macy wrote: > Unfortunately, ZERO_COPY_SOCKETs have long been a known source of > problems. I think also, when a page is copied as part of COW the new > page is unwired (see pmap_copy et al.), this could lead to > socow_iodone unwiring after send a page that was not wired. An added > issue is that parts of the VM assume that COW and wired are mutually > exclusive which the socow code violates. > > At some point in the near future I may be adding support for doing > zero copy send without COW for blocking sockets. The one down side of > this approach is that if you have multiple threads in your process it > widens the window during which they can stomp on data that you're > sending. Nonetheless, this would be a bug in the application code. > More complicated would be zero-copy non-COW send on non-blocking > sockets as it would require an extension to kevent for completion > notification. > > In the meantime, your best bet is to disable ZERO_COPY_SOCKETS. There is a chance this was a recent regression, previously in 7.0 they were believed to work. Kris > > > -Kip > > > > On Nov 13, 2007 1:59 PM, Vivek Khera wrote: >> On Nov 13, 2007, at 4:50 PM, Vlad GALU wrote: >> >>>> vmio = 1 >>>> offset = Unhandled dwarf expression opcode 0x93 >>>> (kgdb) >>>> >>> Do you happen to have ZERO_COPY_SOCKETS in your kernel config? >>> >>> >> Yes, I do. Are they known to be bad under certain loads or just in >> general. I don't have this issue with any other web server running >> the same kernel config but those are amd64 boxes mostly. >> >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > >