On Thu, Nov 08, 2018 at 07:08:50PM -0700, Alan Somers wrote:
> On a fresh install of 12.0-BETA3, I'm seeing processes get stuck in the
> STOP state. Neither SIGCONT nor SIGKILL has any effect. And it's
> reproducible. All I have to do is:
> 1) Login to my login manager, which starts xfce
> 2) St
On a fresh install of 12.0-BETA3, I'm seeing processes get stuck in the
STOP state. Neither SIGCONT nor SIGKILL has any effect. And it's
reproducible. All I have to do is:
1) Login to my login manager, which starts xfce
2) Start firefox
3) kill X
4) Login again
5) ps -ax | egrep '\'
And I see
[ Charset UTF-8 unsupported, converting... ]
>
>
> On 11/8/18 12:25 PM, Ernie Luzar wrote:
> > ftp.freebsd.org/pub/FreeBSD/releases/amd/amd/12.0-BETA3/base.txz
> >
> > /usr/local empty
> > /var/log? empty
> >
> > This is really making testing imposable!
>
> shouldn't both of those directories be
Ok, this one looks interesting.
On Thu, Nov 8, 2018 at 10:39 PM wrote:
>
> FreeBSD-head-armv7-build - Build #2129 (r340262) - Failure
>
> Build information: https://ci.freebsd.org/job/FreeBSD-head-armv7-build/2129/
> Full change log:
> https://ci.freebsd.org/job/FreeBSD-head-armv7-build/2129/cha
On 11/8/18 12:25 PM, Ernie Luzar wrote:
ftp.freebsd.org/pub/FreeBSD/releases/amd/amd/12.0-BETA3/base.txz
/usr/local empty
/var/logĀ empty
This is really making testing imposable!
shouldn't both of those directories be empty in the base.txz file? or is
their another error you are getting?
ftp.freebsd.org/pub/FreeBSD/releases/amd/amd/12.0-BETA3/base.txz
/usr/local empty
/var/log empty
This is really making testing imposable!
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubs
The 12.0-RELEASE schedule has been updated, adding BETA4 to the schedule
in order to provide additional testing for changes that fix a boot time
issue, in addition to allowing more time for packages for arm and arm64
to finish building, before branching releng/12.0 and starting the RC
phase of the
Hi,
I replaced
<< printf("XXX knote %p already in tailq status:%x kq_count:%d [%p %p]
%u\n",kn,kn->kn_status,kq->kq_count,kn->kn_tqe.tqe_next,kn->kn_tqe.tqe_prev,__LINE__);
by
>> panic("XXX knote %p already in tailq status:%x kq_count:%d [%p %p]
%u\n",kn,kn->kn_status,kq->kq_count,kn->kn_tqe.t