> I apologize if this isn't the right group. > But since the stack trace shows esballoc_mblk_free() > and the problem appears to be triggered by the sendfilev64() > system call, this seems the appropriate group. > > We believe we are seeing a panic due to bug #6682131. It has an > identical stack trace and occurs only with a sendfilev() system call > (in our case from in.ftpd). It is completely reproducible. > > We tried the suggestion for 6543412: "set kpm_enable=0" in /etc/system, > but we still get the panic. > > Has anyone else seen this problem? Anyone know the status of this bug?
6682131 is closed as a duplicate of 6543412 which in turn was closed as "not a defect". From a brief examination of the escalations, it appears the reported cases were due to memory corruption caused by a third-party kernel module (MVFS). -- meem _______________________________________________ networking-discuss mailing list [email protected]
