On Sun, 18 Jul 2004, Willem Jan Withagen wrote: > Starting on: > > > - Try compiling IPv6 out of your kernel -- this will turn on the inpcb > > locking assertions, which are compiled out by default because IPv4 and > > IPv6 share the same underlying pcb code and IPv6 does not yet lock that > > correctly in CVS. I have patches that do quite a bit of that in > > Perforce, and sent out an e-mail yesterday to the KAME folk to talk > > about merging strategies. > > > > - If this is a reproduceable problem, could you try disabling SACK and see > > if it changes at all? > > How do I disable SACK?? Probably there's a flag for, but which.... The sysctl net.inet.tcp.sack.enable enables (and disables) SACK. Given some of the other versions of the trace you're reporting, it's seeming less like it's SACK that's causing the problem, but it's definitely worth trying. We could be looking at an issue with the bge driver -- I have some bge cards and will see about sticking one into a machine here for testing. Can you suggest a workload I can try that will reliably generate the panic for you? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert_at_fledge.watson.org Principal Research Scientist, McAfee ResearchReceived on Sun Jul 18 2004 - 17:13:49 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:02 UTC