Re: CURRENT: re(4) crashing system

On Tue, Oct 25, 2016 at 07:03:38AM +0200, Hartmann, O. wrote: > On Tue, 25 Oct 2016 11:05:38 +0900 > YongHyeon PYUN wrote: > [...] > > I'm not sure but it's likely the issue is related with EEE/Green > > Ethernet handling. EEE is negotiated feature with link partner. If > >

Re: stable/11 -r307797 on BPi-M3 (cortex-a7): xgcc's cc1 during lang/gcc6 build gets SIGSYS failures (/usr/ports -r424540)

[A top post noting that user "ast" CSW's are involved and other details in the sequence leading up to the failure.] Using "ktrace -i -t +fw" it looks like every repeat of the problem ends up with the following sort of sequence (a variation is shown later): 34629 cc1 CALL

Re: 11.x deadlocking during pfault (was Re: FreeBSD 11.x grinds to a halt after about 48h of uptime)

On Wed, 2016-10-26 at 18:43:43 +0200, Ulrich Spörlein wrote: > On Mon, 2016-10-24 at 19:43:27 +0200, Ulrich Spörlein wrote: > > On Sat, 2016-10-15 at 09:36:27 -0700, Kevin Oberman wrote: > > > On Sat, Oct 15, 2016 at 9:26 AM, Hans Petter Selasky > > > wrote: > > > > > > > On

11.x deadlocking during pfault (was Re: FreeBSD 11.x grinds to a halt after about 48h of uptime)

On Mon, 2016-10-24 at 19:43:27 +0200, Ulrich Spörlein wrote: > On Sat, 2016-10-15 at 09:36:27 -0700, Kevin Oberman wrote: > > On Sat, Oct 15, 2016 at 9:26 AM, Hans Petter Selasky > > wrote: > > > > > On 10/15/16 18:18, Ulrich Spörlein wrote: > > > > > >> Hey all, while 11.x is