I get an builderror on my 11.1 stable machine after the latest svn
update Revision: 330235
--
>>> stage 3.1: building everything
--
cd /usr/obj/usr/src/sys/KRNL; MAKEOBJDIRPREFI
On Thu, 1 Mar 2018 10:48+0100, Johan Hendriks wrote:
> I get an builderror on my 11.1 stable machine after the latest svn
> update Revision: 330235
>
>
> --
> >>> stage 3.1: building everything
>
On Thu, 1 Mar 2018 14:09+0100, Trond Endrestøl wrote:
> If you revert to r330229, i.e. svn up -r330229 /usr/src, you should be
> able to build a working kernel.
>
> r330230 added "17" to line 1939 of sys/conf/files breaking iwm(fw),
> and I suspect "17" should be "22", or maybe the "D" should b
On Thu, Mar 1, 2018 at 7:34 AM, Trond Endrestøl
wrote:
> On Thu, 1 Mar 2018 14:09+0100, Trond Endrestøl wrote:
>
>> If you revert to r330229, i.e. svn up -r330229 /usr/src, you should be
>> able to build a working kernel.
>>
>> r330230 added "17" to line 1939 of sys/conf/files breaking iwm(fw),
>>
Would be broken by r330233.
This revision assumes member c_pktflags in struct ieee80211_rx_stats,
but this addition (done at r306837 on head) is NOT yet MFC'ed.
Reverting r330233 allowed me build, install and boot kernel.
*I'm not shure MFC'ing r306837 is sufficent or not.
OTOH, not shure MFC'i
On 1 March 2018 at 05:34, Trond Endrestøl
wrote:
> On Thu, 1 Mar 2018 14:09+0100, Trond Endrestøl wrote:
>
>> If you revert to r330229, i.e. svn up -r330229 /usr/src, you should be
>> able to build a working kernel.
>>
>> r330230 added "17" to line 1939 of sys/conf/files breaking iwm(fw),
>> and I
Op 01/03/2018 om 17:03 schreef Eitan Adler:
> On 1 March 2018 at 05:34, Trond Endrestøl
> wrote:
>> On Thu, 1 Mar 2018 14:09+0100, Trond Endrestøl wrote:
>>
>>> If you revert to r330229, i.e. svn up -r330229 /usr/src, you should be
>>> able to build a working kernel.
>>>
>>> r330230 added "17" t
Hi sta...@freebsd.org
I think I have found a memory leak with inetd on 10.3-STABLE
(server runs in a VM); server ran out of swap.
top
Mem: 34M Active, 791M Inact, 387M Wired, 200K Cache, 212M Buf, 759M Free
Swap: 614M Total, 605M Used, 8744K Free, 98% Inuse
uptime
Hi,
I am trying to get a FreeBSD NFS 4.1 export working with VMware Esxi 6.5u1, but
it is always mounted as read only.
After some research, I found out that this is a known problem, and there are
threads about this from 2015 also in the mailinglist archive.
As it seems VMware will not change t
On Thu, 1 Mar 2018 08:03-0800, Eitan Adler wrote:
> >> I hope these errors will be corrected shortly.
>
> Build error is fixed. Sorry for the breakage
>
> > r330229 is also broken. I had to revert to r330113 to avoid any of the
> > recent iwm commits.
>
> Did r330242 fix the issue for you?
Yes
10 matches
Mail list logo