Program crashes after 320666

[Kevin Oberman]

multimedia/avidemux_qt4 has started dumping core with segfaults and other
errors in libthread called from Qt4. I am suspicious that the real problem
is in Qt4 and those errors were previously not detected and usually not
causing a problem.

The problem shows up with kernels at r320666 and later. The update on July
5 was:
Add MAP_GUARD and use it for stack protection.

Should I open a ticket for the Qt4 or should I spend more effort on whether
it might be a kernel issue. (Pretty sure it's Qt4 at fault.) I might also
look into updating the port to use Qr5 as Qt4 is clearly starting to bitrot
and support for Qt5 has already been added upstream.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 221146] [LAGG] Problem with second laggport

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

Matt Joras  changed:

   What|Removed |Added

 CC||mjo...@freebsd.org

--- Comment #12 from Matt Joras  ---
Does this only happen with LACP or does it happen with any lagg type (e.g.
failover)?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 221146] [LAGG] Problem with second laggport

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

--- Comment #11 from Konrad  ---
Yes, its reproducible. I change lagg configuration in rc.conf and reboot
machine.

if lagg0 will start with "ix1 flags=0" ix1 will have always "no carrier" even
if I remove from laggport. Manually removed ix1 and netif restart does no fix
the problem (ix1 still has "no carrier"), only reboot.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 221146] [LAGG] Problem with second laggport

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

--- Comment #10 from Andrey V. Elsukov  ---
(In reply to Konrad from comment #9)
> I set LAGG on igb0 and igb1 and seems to be ok:
> but when ix's ports are configured as lagg1, all laggports work properly.
> When I  switch ix's ports as lagg0 and first in cloned_interfaces the
> problem appears:

Is it reproducible? Are you doing this in runtime manually without reboot?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[Bug 221146] [LAGG] Problem with second laggport

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

--- Comment #9 from Konrad  ---
I set LAGG on igb0 and igb1 and seems to be ok:

lagg0: flags=8843 metric 0 mtu 1500
   
options=6403bb
ether 00:1e:67:27:1d:5e
inet 192.168.202.254 netmask 0xff00 broadcast 192.168.202.255 
nd6 options=29
media: Ethernet autoselect
status: active
groups: lagg 
laggproto lacp lagghash l2,l3,l4
laggport: igb0 flags=1c
laggport: igb1 flags=1c
lagg1: flags=8843 metric 0 mtu 1500
   
options=e400bb
ether 0c:c4:7a:bd:65:58
inet 192.168.202.254 netmask 0xff00 broadcast 192.168.202.255 
nd6 options=29
media: Ethernet autoselect
status: active
groups: lagg 
laggproto lacp lagghash l2,l3,l4
laggport: ix0 flags=1c
laggport: ix1 flags=1c




but when ix's ports are configured as lagg1, all laggports work properly. When
I  switch ix's ports as lagg0 and first in cloned_interfaces the problem
appears:



lagg0: flags=8843 metric 0 mtu 1500
   
options=e400bb
ether 0c:c4:7a:bd:65:58
inet 192.168.202.254 netmask 0xff00 broadcast 192.168.202.255 
nd6 options=29
media: Ethernet autoselect
status: active
groups: lagg 
laggproto lacp lagghash l2,l3,l4
laggport: ix0 flags=1c
laggport: ix1 flags=0<>
lagg1: flags=8843 metric 0 mtu 1500
   
options=6403bb
ether 00:1e:67:27:1d:5e
inet 192.168.202.254 netmask 0xff00 broadcast 192.168.202.255 
nd6 options=29
media: Ethernet autoselect
status: active
groups: lagg 
laggproto lacp lagghash l2,l3,l4
laggport: igb0 flags=1c
laggport: igb1 flags=1c

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"