On Wed, Dec 09, 2020 at 02:00:37PM +1100, Dewayne Geraghty wrote:
! On a jail with config:
! exec.start = "/bin/sh -x /etc/rc";
! exec.stop = "/bin/sh /etc/rc.shutdown";
! exec.clean;
!
! test_prod { jid=7; persist; ip4.addr =
! "10.0.7.96,10.0.5.96,127.0.5.96"; devfs_ruleset = "6";
!
Peter,
I’m not interested in discussing software development methodology
here.
Please drop me from this thread. Let me know if/when you have a test
case I can work from.
Regards,
Kristof
On 9 Dec 2020, at 11:54, Peter wrote:
On Tue, Dec 08, 2020 at 07:51:07PM -0600, Kyle Evans wrote:
!
On Tue, Dec 08, 2020 at 07:51:07PM -0600, Kyle Evans wrote:
! You seem to have misinterpreted this; he doesn't want to narrow it
! down to one bug, he wants simple steps that he can follow to reproduce
Maybe I did misinterpret, but then I don't really understand it.
I would suppose, when
On 9 Dec 2020, at 2:31, Peter wrote:
On Tue, Dec 08, 2020 at 08:02:47PM +0100, Kristof Provost wrote:
! > Sorry for the bad news.
! >
! You appear to be triggering two or three different bugs there.
That is possible. Then there are two or three different bugs in the
production code.
In any
On Tue, Dec 8, 2020 at 7:45 PM Peter wrote:
>
>
> On Tue, Dec 08, 2020 at 08:02:47PM +0100, Kristof Provost wrote:
> > Can you reduce your netgraph use case to a small test case that can trigger
> ? the problem?
>
> I'm sorry, I fear I don't get Your point.
> Assumed there are actually two or
On Tue, Dec 08, 2020 at 08:02:47PM +0100, Kristof Provost wrote:
! > Sorry for the bad news.
! >
! You appear to be triggering two or three different bugs there.
That is possible. Then there are two or three different bugs in the
production code.
In any case, my current workaround, i.e.
Here is the next funny crashdump - I obtained this one twice
and also the sysctl_rtsock() again.
I can reproduce this by just starting and stopping a most simple jail
that does only
exec.start = "/bin/sleep 4 &";
(And as usual, when I let it time out, nothing bad happens.)
Fatal trap 9:
On 8 Dec 2020, at 19:49, Peter wrote:
On Tue, Dec 08, 2020 at 04:50:00PM +0100, Kristof Provost wrote:
! Yeah, the bug is not exclusive to epair but that’s where it’s
most easily
! seen.
Ack.
! Try
http://people.freebsd.org/~kp/0001-if-Fix-panic-when-destroying-vnet-and-epair-simultan.patch
On Tue, Dec 08, 2020 at 04:50:00PM +0100, Kristof Provost wrote:
! Yeah, the bug is not exclusive to epair but that’s where it’s most easily
! seen.
Ack.
! Try
http://people.freebsd.org/~kp/0001-if-Fix-panic-when-destroying-vnet-and-epair-simultan.patch
Great, thanks a lot.
Now I have bad
On 8 Dec 2020, at 0:34, Peter wrote:
Hi Kristof,
it's great to read You!
On Mon, Dec 07, 2020 at 09:11:32PM +0100, Kristof Provost wrote:
! That smells a lot like the epair/vnet issues in bugs 238870, 234985,
244703,
! 250870.
epair? No. It is purely Netgrh here.
Yeah, the bug is not
Hi Kristof,
it's great to read You!
On Mon, Dec 07, 2020 at 09:11:32PM +0100, Kristof Provost wrote:
! That smells a lot like the epair/vnet issues in bugs 238870, 234985, 244703,
! 250870.
epair? No. It is purely Netgraph here.
! I pushed a fix for that in CURRENT in r368237. It’s
On 7 Dec 2020, at 13:54, Peter wrote:
After clean upgrade (from source) from 11.4 to 12.2-p1 my jails do
no longer work correctly.
Old-fashioned jails seem to work, but most are VIMAGE+NETGRAPH style,
and do not work properly.
All did work flawlessly for nearly a year with Rel.11.
If I start
After clean upgrade (from source) from 11.4 to 12.2-p1 my jails do
no longer work correctly.
Old-fashioned jails seem to work, but most are VIMAGE+NETGRAPH style,
and do not work properly.
All did work flawlessly for nearly a year with Rel.11.
If I start 2-3 jails, and then stop them again,
13 matches
Mail list logo
