You're helpful reply doesn't seem to include any information on where to upload a crash dump, if that's what is being asked. I haven't dealt with them before. Perhaps you'd be so kind as to direct?

A reply that helps work around a problem is always welcome, especially when it keeps a remotely located host from continuously rebooting.

Paul Saab wrote:

Arjan Van Leeuwen wrote:

I had a panic that looked a lot like this (panic in swi, came up when

I had some network traffic), and it's also been reported by other
people than me. Turning of SACK seems to work for most people (at
least it worked for me). Put net.inet.tcp.sack.enable=0 in
/etc/sysctl.conf.


And how exactly is this supposed to help anyone fix the problem. If you provide crashdumps then solving the problem becomes much easier, but nothing will get fixed if you just turn it off.


_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to