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
Hi,
On Fri, May 31, 2013 at 02:23:01PM -0400, Masao Uebayashi wrote:
> This is a newly written driver for VMware VMXNET3 ethernet controller.
>
I created a manpage that I will commit shortly after the driver is in.
reyk
Index:
> I'm voting for committing it and to do further changes in the tree.
that's the right process.
Hi,
this is some nice work!
The new virtual VMXNET3 chipset supports a few features that haven't
been available in the previous chipsets, including "VLAN Guest Tagging
(VGT)", or simply the ability to pass tagged VLANs from VMware hosts
to external switches, and checksum offload
This is a newly written driver for VMware VMXNET3 ethernet controller.
- vic(4) was not used as a base because VMXNET3 is very different from
previous VMXNET versions.
- Simple test shows that performance is comparable to VMXNET3 driver from
open-vm-tools.
- Man page is missing (ongoing
On Fri, Jul 20, 2012 at 09:24:51AM +0200, Johan Ryberg wrote:
> Thanks =)
>
> Do you know if OpenBSD current support vmxnet3? vlan has been
> problematic last time I tested in 4.9
And do you have updated if_vic.c ?
I'm not programmer :(
jirib
Thanks =)
Do you know if OpenBSD current support vmxnet3? vlan has been
problematic last time I tested in 4.9
Best regards Johan Ryberg
2012/7/19 Jiri B :
> Hello,
>
> to make vmxnet3 recognized.
>
> jirib
>
> $ cvs diff -uNp pci
Hello,
to make vmxnet3 recognized.
jirib
$ cvs diff -uNp pcidevs
Index
On 2012/04/23 10:32, mxb wrote:
> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120329
> Thunderbird/11.0.1
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Ne point resending now as it's simple enough to redo, but Thunderbird
mangled your diff, see this for inf
On 04/23/2012 10:39 AM, Brad Smith wrote:
On 23/04/12 4:32 AM, mxb wrote:
Diff below adds vmxnet3 to pcidevs.
vmxnet and vmxnet2 have the same PCI ID and thus catched by the same
macro - VMWARE NET.
While there, remove \t with space for MACHINE_2
The PCI id entries are sorted so this new
On 23/04/12 4:32 AM, mxb wrote:
Diff below adds vmxnet3 to pcidevs.
vmxnet and vmxnet2 have the same PCI ID and thus catched by the same
macro - VMWARE NET.
While there, remove \t with space for MACHINE_2
The PCI id entries are sorted so this new addition needs to be
moved further down so it
Diff below adds vmxnet3 to pcidevs.
vmxnet and vmxnet2 have the same PCI ID and thus catched by the same
macro - VMWARE NET.
While there, remove \t with space for MACHINE_2
//maxim
Index: sys/dev/pci/pcidevs
===
RCS file: /cvs
17 matches
Mail list logo