Date: Wed, 27 May 2009 18:50:03 GMT From: "Steven G. Kargl" <kargl@troutmask.apl.washington.edu> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/132827: [vm] [panic] vm_page_free_toq: freeing mapped page Message-ID: <200905271850.n4RIo34w081657@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/132827; it has been noted by GNATS. From: "Steven G. Kargl" <kargl@troutmask.apl.washington.edu> To: Alan Cox <alc@cs.rice.edu> Cc: bug-followup@FreeBSD.org Subject: Re: kern/132827: [vm] [panic] vm_page_free_toq: freeing mapped page Date: Wed, 27 May 2009 11:43:46 -0700 (PDT) Alan Cox wrote: > Steven G. Kargl wrote: > > Alan Cox wrote: > > > >> There has been no reported re-occurrence of this assertion failure since > >> the submitter removed ZERO_COPY_SOCKETS from his kernel configuration. > >> > > > > Yes, that is correct. The panics stopped after removal of > > ZERO_COPY_SOCKETS. I'd suggest adding a big warning in > > the various NOTES files that ZERO_COPY_SOCKETS is broken. > > > > > > I will gladly commit appropriately frightening language. Send me a > patch. :-) > Index: NOTES =================================================================== --- NOTES (revision 191256) +++ NOTES (working copy) @@ -930,7 +930,9 @@ # receiving data via a socket. The send side works for any type of NIC, # the receive side only works for NICs that support MTUs greater than the # page size of your architecture and that support header splitting. See -# zero_copy(9) for more details. +# zero_copy(9) for more details. This option is assocated with a rare, +# but possible, kernel panic in vm_page_free_toq(). See kern/132827 for +# additional details. options ZERO_COPY_SOCKETS -- Steve http://troutmask.apl.washington.edu/~kargl/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905271850.n4RIo34w081657>