There's something fishy going on here. I have a feeling that the issue may be related to the reallocation fragmentation -- we might be running the system out of KVM and there are *NO* NULL checks in the file descriptor allocation code. I'm trying to instrument the code and duplicate the problem now, and will go from there. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: Wierd AMD panics caused by VMWare? David Gilbert
- Re: Wierd AMD panics caused by VMWare? Nick Sayer
- Re: Wierd AMD panics caused by VMWare? David Gilbert
- Re: Wierd AMD panics caused by VMWare? Bruce Evans
- Re: Wierd AMD panics caused by VMWare? Matthew Dillon
- RE: Wierd AMD panics caused by VMWare? Nick Sayer
- Re: Wierd AMD panics caused by VMWare? Bruce Evans
- Re: Wierd AMD panics caused by VMWare? Matthew Dillon
- Re: Wierd AMD panics caused by VMWare... Matthew Dillon
- Re: Wierd AMD panics caused by VMWare... Matthew Dillon
- Patch to try (was Re: Wierd AMD panic... Matthew Dillon
- Re: Patch to try (was Re: Wierd A... Matthew Dillon
- Patch to try (was Re: Wierd AMD p... David Gilbert
- Re: Patch to try (was Re: Wierd A... Bruce Evans