I created a new patch on reviews.freebsd.org
https://reviews.freebsd.org/D17411
I need to wait for mentor's approval before writing to re@
Thanks,
Vincenzo
Il giorno gio 4 ott 2018 alle ore 17:25 Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> ha scritto:
> > Hi Rodney,
> > Sure. Is
> Hi Rodney,
> Sure. Is there a specific procedure for this, or should I just send the
> .diff to r...@freebsd.org?
Yes, there is a procedure:
https://wiki.freebsd.org/Releng/ChangeRequestGuidelines
the specific details for when the release is ^head is
towards the bottom.
Thanks again,
>
> Th
Hi Rodney,
Sure. Is there a specific procedure for this, or should I just send the
.diff to r...@freebsd.org?
Thanks,
Vincenzo
Il giorno gio 4 ott 2018 alle ore 17:03 Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> ha scritto:
> > Hi,
> > I fixed this upstream in this commit
> >
> h
> Hi,
> I fixed this upstream in this commit
> https://github.com/luigirizzo/netmap/commit/282f404ccb4fc777056a591127060e29657c9ab7
> I will apply the change into FreeBSD as soon as HEAD thaws.
This appears to be a man page change only,
please do submit that to r...@freebsd.org to be
committed n
Hi,
I fixed this upstream in this commit
https://github.com/luigirizzo/netmap/commit/282f404ccb4fc777056a591127060e29657c9ab7
I will apply the change into FreeBSD as soon as HEAD thaws.
Cheers,
Vincenzo
Il giorno gio 4 ott 2018 alle ore 00:36 K. Macy ha
scritto:
> On Fri, Aug 31, 2018 at 6:
On Fri, Aug 31, 2018 at 6:50 PM John-Mark Gurney wrote:
>
> First, does vale work for anyone? At least one of the documented
> commands in vale(4) does not work.
>
The documentation with respect to naming is wrong. I didn't have a bit
when I was using it so never got around to fixing it.
> Afte
Il giorno gio 6 set 2018 alle ore 08:35 Marko Zec ha scritto:
> On Wed, 5 Sep 2018 17:42:06 -0700
> John-Mark Gurney wrote:
>
> > Marko Zec wrote this message on Wed, Sep 05, 2018 at 12:47 +0200:
> > > On Wed, 5 Sep 2018 12:36:38 +0200
> > > Vincenzo Maffione wrote:
> > >
> > > > Hi Marko,
> >
On Wed, 5 Sep 2018 17:42:06 -0700
John-Mark Gurney wrote:
> Marko Zec wrote this message on Wed, Sep 05, 2018 at 12:47 +0200:
> > On Wed, 5 Sep 2018 12:36:38 +0200
> > Vincenzo Maffione wrote:
> >
> > > Hi Marko,
> > > Thanks a lot for identifying the problem.
> > > If I understand correctl
Marko Zec wrote this message on Wed, Sep 05, 2018 at 12:47 +0200:
> On Wed, 5 Sep 2018 12:36:38 +0200
> Vincenzo Maffione wrote:
>
> > Hi Marko,
> > Thanks a lot for identifying the problem.
> > If I understand correctly, simply adding -D VIMAGE here
> > https://github.com/luigirizzo/netmap/blo
On Wed, 5 Sep 2018 12:36:38 +0200
Vincenzo Maffione wrote:
> Hi Marko,
> Thanks a lot for identifying the problem.
> If I understand correctly, simply adding -D VIMAGE here
> https://github.com/luigirizzo/netmap/blob/master/sys/modules/netmap/Makefile#L11
> would at least mitigate the issue.
>
Hi Marko,
Thanks a lot for identifying the problem.
If I understand correctly, simply adding -D VIMAGE here
https://github.com/luigirizzo/netmap/blob/master/sys/modules/netmap/Makefile#L11
would at least mitigate the issue.
If you think I'm right I'll just add it.
Thanks,
Vincenzo
Il giorno m
On Tue, 4 Sep 2018 20:18:29 +0200
Vincenzo Maffione wrote:
> Hi,
> I don't think the panic depends on the architecture. Also, it does
> not depend on using emulated mode or not.
> We have seen this happening on x86_64 on FreeBSD 12 head.
>
> As John-Mark says, kdloading netmap.ko is not enough
Hi,
I don't think the panic depends on the architecture. Also, it does not
depend on using emulated mode or not.
We have seen this happening on x86_64 on FreeBSD 12 head.
As John-Mark says, kdloading netmap.ko is not enough. You need to open a
netmap port corresponding
to any network interface,
Marko Zec wrote this message on Tue, Sep 04, 2018 at 16:43 +0200:
> On Sat, 1 Sep 2018 14:11:23 -0700
> John-Mark Gurney wrote:
> > Vincenzo Maffione wrote this message on Sat, Sep 01, 2018 at 22:25
> > +0200:
> ...
> > > On x86_64 netmap is not built as a module, so everything works
> > > fine. I
On Sat, 1 Sep 2018 14:11:23 -0700
John-Mark Gurney wrote:
> Vincenzo Maffione wrote this message on Sat, Sep 01, 2018 at 22:25
> +0200:
...
> > On x86_64 netmap is not built as a module, so everything works
> > fine. I don't see any reason why it should be a module in aarch64.
>
> Well, sys/mod
Il giorno sab 1 set 2018 alle ore 23:11 John-Mark Gurney
ha scritto:
> Vincenzo Maffione wrote this message on Sat, Sep 01, 2018 at 22:25 +0200:
> > Il giorno sab 1 set 2018 alle ore 03:50 John-Mark Gurney <
> j...@funkthat.com>
> > ha scritto:
> >
> > > First, does vale work for anyone? At leas
Vincenzo Maffione wrote this message on Sat, Sep 01, 2018 at 22:25 +0200:
> Il giorno sab 1 set 2018 alle ore 03:50 John-Mark Gurney
> ha scritto:
>
> > First, does vale work for anyone? At least one of the documented
> > commands in vale(4) does not work.
> >
> > After manually building the net
Il giorno sab 1 set 2018 alle ore 03:50 John-Mark Gurney
ha scritto:
> First, does vale work for anyone? At least one of the documented
> commands in vale(4) does not work.
>
> After manually building the netmap module and loading it:
> # tcpdump -ni vale-a:1
> 313.748851 nm_open [947] invalid b
First, does vale work for anyone? At least one of the documented
commands in vale(4) does not work.
After manually building the netmap module and loading it:
# tcpdump -ni vale-a:1
313.748851 nm_open [947] invalid bridge name vale-a:1
tcpdump: netmap open: cannot access vale-a:1: Invalid argument
19 matches
Mail list logo
