On 10 Apr 2017, at 12:10, peter.b...@bsd4all.org wrote:
There have been issues with pf if I recall correctly. I currently have
issues with stable, pf and vnet. There is an issue with pf table
entries when an interface is moved to a different vnet.
Does anyone no if there is a specific fix for
Hi,
There is also this one:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213673
It's about memory leak with pf tables + vnet, but the problem results
in panic, which is quite easily reproduced.
Ari S.
On 10.4.2017 17:39, Ernie Luzar wrote:
To the VNET (VIMAGE) update project team m
On Mon, 10 Apr 2017 21:04:04 +0200
"O. Hartmann" wrote:
> Am Mon, 10 Apr 2017 21:59:00 +0300
> Toomas Soome schrieb:
>
> > > On 10. apr 2017, at 21:04, O. Hartmann
> > > wrote:
> > >
> > > Am Mon, 10 Apr 2017 16:14:21 +0300
> > > Toomas Soome schrieb:
> > >
> > >>> On 10. apr 2017, at 1
On 10 Apr 2017, at 20:59, peter.b...@bsd4all.org wrote:
No problem. Although pf is not used the vnet_destroy seems to be the
issue. Some parts are not virtualized and the
vnet_destroy->vnet_pf_uninit teardown happens on the host vnet so to
speak.
The base system VNET is not shutdown; it nev
No problem. Although pf is not used the vnet_destroy seems to be the issue.
Some parts are not virtualized and the vnet_destroy->vnet_pf_uninit teardown
happens on the host vnet so to speak.
> On 10 Apr 2017, at 22:11, Ernie Luzar wrote:
>
> peter.b...@bsd4all.org wrote:
>> Well, in my case i
peter.b...@bsd4all.org wrote:
Well, in my case it panic’ed on 11-stable. I’m only using pf on the
host, not in the jail. I’m using Devin Teske’s jng to create a netgraph
bridge. It is my intention to use the netgrpah bridge with bhyve as well.
I also tested using Devin Teske’s jng to create
Am Mon, 10 Apr 2017 21:59:00 +0300
Toomas Soome schrieb:
> > On 10. apr 2017, at 21:04, O. Hartmann wrote:
> >
> > Am Mon, 10 Apr 2017 16:14:21 +0300
> > Toomas Soome schrieb:
> >
> >>> On 10. apr 2017, at 15:58, Hartmann, O. wrote:
> >>>
> >>> After today's update to r316677, some UEFI b
> On 10. apr 2017, at 21:04, O. Hartmann wrote:
>
> Am Mon, 10 Apr 2017 16:14:21 +0300
> Toomas Soome schrieb:
>
>>> On 10. apr 2017, at 15:58, Hartmann, O. wrote:
>>>
>>> After today's update to r316677, some UEFI boxes (Fujitsu Celsius M740
>>> XEON) reject to boot properly. They die immed
There is a similar thread with subject: 'how to mark llvm* forbidden?'
going on right now on this list.
Regards,
Ronald.
On Mon, 10 Apr 2017 14:10:03 +0200, O. Hartmann
wrote:
We build pretty often world and ports.
With poudriere as port building backend, The daily/weekly builds have
Am Mon, 10 Apr 2017 16:14:21 +0300
Toomas Soome schrieb:
> > On 10. apr 2017, at 15:58, Hartmann, O. wrote:
> >
> > After today's update to r316677, some UEFI boxes (Fujitsu Celsius M740
> > XEON) reject to boot properly. They die immediately after
> > loading /boot/loader.efi and jump into loa
On 4/7/2017 12:13 PM, Ngie Cooper (yaneurabeya) wrote:
> Hi,
> I ran into this error when trying to run a meta mode build (for the
> first time). It might be related to the recent assym* ordering changes.
> Thanks!
> -Ngie
>
> $ cat /etc/src-env.conf
> WITH_AUTO_OBJ= yes
> WITH_META_MODE=
peter.b...@bsd4all.org wrote:
Well, in my case it panic’ed on 11-stable. I’m only using pf on the
host, not in the jail. I’m using Devin Teske’s jng to create a netgraph
bridge. It is my intention to use the netgrpah bridge with bhyve as well.
The panic (one-time) happened in pfioctl when I re
To the VNET (VIMAGE) update project team members
Release 11.0 has some out standing VNET (VIMAGE) PR's that need addressing.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212013
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21203
Well, in my case it panic’ed on 11-stable. I’m only using pf on the host, not
in the jail. I’m using Devin Teske’s jng to create a netgraph bridge. It is my
intention to use the netgrpah bridge with bhyve as well.
The panic (one-time) happened in pfioctl when I refreshed the rules. I suspect
th
peter.b...@bsd4all.org wrote:
There have been issues with pf if I recall correctly. I currently have issues
with stable, pf and vnet. There is an issue with pf table entries when an
interface is moved to a different vnet.
Does anyone no if there is a specific fix for this that hasn’t been port
> On 10. apr 2017, at 15:58, Hartmann, O. wrote:
>
> After today's update to r316677, some UEFI boxes (Fujitsu Celsius M740
> XEON) reject to boot properly. They die immediately after
> loading /boot/loader.efi and jump into loader prompt:
>
> [...]
> \
> can't load 'kernel'
>
>
> I had to in
After today's update to r316677, some UEFI boxes (Fujitsu Celsius M740
XEON) reject to boot properly. They die immediately after
loading /boot/loader.efi and jump into loader prompt:
[...]
\
can't load 'kernel'
I had to investigate with an USB flashdrive the filesystem, but
everything seems to b
We build pretty often world and ports.
With poudriere as port building backend, The daily/weekly builds have now grown
in compile time significantly since approx. the introduction of LLVM 4.0 into
FreeBSD.
The build box is a LGA1150 IvyBridge XEON system with 3,4 GHz and 16 GB RAM.
The configurat
There have been issues with pf if I recall correctly. I currently have issues
with stable, pf and vnet. There is an issue with pf table entries when an
interface is moved to a different vnet.
Does anyone no if there is a specific fix for this that hasn’t been ported to
stable? I haven’t had the
19 matches
Mail list logo
