On Wed, Jun 03, 2015 at 23:14 +0200, mxb wrote:
>
> Any chance to get this committed?
> Stepped on it once more without this patch.
>
I'd like to. OKs?
> //mxb
>
> On 2015-05-22 19:53, Mike Belopuhov wrote:
> >vmx doesn't check if it's wasn't stopped before calling rx/tx
> >interrupt routines
Any chance to get this committed?
Stepped on it once more without this patch.
//mxb
On 2015-05-22 19:53, Mike Belopuhov wrote:
On Fri, May 22, 2015 at 19:35 +0200, mxb wrote:
Hey,
got a panic as of todays ‘cvs up’
trace below
panic: vmxnet3_rxintr: NULL ring->m[44]
Stopped at Debugger+0
On Fri, May 22 2015 at 35:19, mxb wrote:
> Hey,
Hello,
> got a panic as of todays ‘cvs up’
> trace below
I got nearly the same panic stopping a 5.7 host
> panic: vmxnet3_rxintr: NULL ring->m[44]
> Stopped at Debugger+0x9: leave
> RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORT
Not sure if I’ll be able to reproduce this at all.
Never seen this before.
But diff is applied.
//mxb
> On 22 maj 2015, at 19:53, Mike Belopuhov wrote:
>
> On Fri, May 22, 2015 at 19:35 +0200, mxb wrote:
>>
>> Hey,
>> got a panic as of todays ‘cvs up’
>> trace below
>>
>> panic: vmxnet3_rxint
On Fri, May 22, 2015 at 19:35 +0200, mxb wrote:
>
> Hey,
> got a panic as of todays ‘cvs up’
> trace below
>
> panic: vmxnet3_rxintr: NULL ring->m[44]
> Stopped at Debugger+0x9: leave
> RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
> IF RUNNING SMP, USE 'mach
Hey,
got a panic as of todays ‘cvs up’
trace below
panic: vmxnet3_rxintr: NULL ring->m[44]
Stopped at Debugger+0x9: leave
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
IF RUNNING SMP, USE 'mach ddbcpu <#>' AND 'trace' ON OTHER PROCESSORS, TOO.
DO NOT EVEN BOTH
