On Tue, Sep 11, 2018 at 10:21:31AM -0700, Jeffrey Bouquet wrote:
> I'm running v12 as HEAD [ 12.0-CURRENT]
>
> And am at a loss as to how to change it to 12.0-STABLE vs one day
> running a non-rebuilt 13.0-CURRENT
>
> Without risking a scenario such as:
>svn up 12.0, fail for some reason
>> /usr/src/tests/sys/kern/ptrace_test.c:3465: WSTOPSIG(status) == SIGABRT not
>> met [0.017s]
>> usr.bin/indent/functional_test:nsac -> failed: atf-check failed; see the
>> output of the test for details [0.151s]
>> usr.bin/indent/functional_test:sac -> fail
On 25/08/2018 09:32, Ali Abdallah wrote:
> Isn't Intel supposed to be working on a native drm driver for FreeBSD?
>
> https://bwidawsk.net/blog/index.php/2018/06/i965-compiler-architecture-from-2015/
…
Not that I can see.
A more recent blog post
On 22/08/2018 17:50, Pete Wright wrote:
>
> On 8/22/18 2:11 AM, Graham Perrin wrote:
>> HP EliteBook 8570p with AMD 'Thames' Radeon HD 7570M.
…
>> With and without drm-next-kmod:
>> if boot is hybrid UEFI with CSM,
>> then suspend occurs, but resume fails. No beep, the computer restarts.
>>
>>
On Tue, Sep 11, 2018 at 06:55:56PM -0400, Shawn Webb wrote:
> On Tue, Sep 11, 2018 at 03:58:02PM -0400, Michael W. Lucas wrote:
> >
> > Hi,
> >
> > storm~;uname -a
> > FreeBSD storm 12.0-ALPHA4 FreeBSD 12.0-ALPHA4 #10 r338496: Thu Sep 6
> > 12:29:00 EDT 2018
> On 11 September 2018 at 07:35, Tomoaki AOKI wrote:
> > I prefer releng, rather than stable, to make it default.
> > Binary releases requiring reproducible builds are built from
> > release and releng branches.
>
> This might be the reasonable long-term strategy, but we don't yet have
>
-CURRENT users, in svn rS338602, 'options NUMA' has just been enabled
for amd64 GENERIC and MINIMAL kernels.
This should provide good effect to systems with more than one physical
CPU with associated memory, certain high core count Intel chips when
configured to use Cluster-on-Die or
Eric van Gyzen wrote in :
|On 9/11/18 10:04 AM, Steffen Nurpmeso wrote:
|> Alan Somers wrote in w...@mail.gmail.com>:
|>|Don't worry Steffen. Python won't be a build requirement for FreeBSD \
|>|even after Eric's patch. His Python script will only need to be run \
|>|whenever IANA
On Tue, Sep 11, 2018 at 03:58:02PM -0400, Michael W. Lucas wrote:
>
> Hi,
>
> storm~;uname -a
> FreeBSD storm 12.0-ALPHA4 FreeBSD 12.0-ALPHA4 #10 r338496: Thu Sep 6
> 12:29:00 EDT 2018 root@storm:/usr/obj/usr/src/amd64.amd64/sys/GENERIC
> amd64
>
> It appears that exec.clean is busted.
Hiya,
I'm currently evaluating two classes of server which we source through NEC.
However, the motherboards for these machines are HP. I can routinely panic both
of these machines using 12.0-A4, as well as 11.1-R with a shoehorned in
SES/SMARTPQI driver, and 11.2-R with its native SES/SMARTPQI
On 9/10/18 8:55 PM, Pete Wright wrote:
> On 9/10/18 5:41 PM, Mark Johnston wrote:
>> On Mon, Sep 10, 2018 at 12:48:56PM -0700, Pete Wright wrote:
>>> On 9/10/18 11:26 AM, Mark Johnston wrote:
Hi,
Support for boot-time loading of Intel microcode updates has landed in
the kernel
Hi,
storm~;uname -a
FreeBSD storm 12.0-ALPHA4 FreeBSD 12.0-ALPHA4 #10 r338496: Thu Sep 6 12:29:00
EDT 2018 root@storm:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
It appears that exec.clean is busted. Here's my jail.conf:
---
$j="/jail";
path="$j/$name";
On 11 September 2018 at 07:35, Tomoaki AOKI wrote:
> I prefer releng, rather than stable, to make it default.
> Binary releases requiring reproducible builds are built from
> release and releng branches.
This might be the reasonable long-term strategy, but we don't yet have
experience running
I'm running v12 as HEAD [ 12.0-CURRENT]
And am at a loss as to how to change it to 12.0-STABLE vs one day
running a non-rebuilt 13.0-CURRENT
Without risking a scenario such as:
svn up 12.0, fail for some reason to be able to build the GPU driver, so I
should
have stuck with svn up 13.0
ed; see the
> output of the test for details [0.151s]
> usr.bin/indent/functional_test:sac -> failed: atf-check failed; see the
> output of the test for details [0.150s]
> ===> Summary
> Results read from
> /root/.kyua/store/results.usr_tests.20180911-070147-413583.db
&g
On 9/11/18 10:04 AM, Steffen Nurpmeso wrote:
Alan Somers wrote in :
|Don't worry Steffen. Python won't be a build requirement for FreeBSD \
|even after Eric's patch. His Python script will only need to be run \
|whenever IANA
|updates its database, and the results will be checked into
Alan Somers wrote in :
|Don't worry Steffen. Python won't be a build requirement for FreeBSD \
|even after Eric's patch. His Python script will only need to be run \
|whenever IANA
|updates its database, and the results will be checked into source contro\
|l. So for a normal user, there
On Tue, Sep 11, 2018 at 10:20:56AM +0200, Andrea Venturoli wrote:
> On 9/10/18 8:26 PM, Mark Johnston wrote:
> > Hi,
> >
> > Support for boot-time loading of Intel microcode updates has landed in
> > the kernel in r337715, and in the sysutils/devcpu-data port as of 1.20.
>
> Thanks for your
On Tue, Sep 11, 2018 at 03:28:15PM +0100, tech-lists wrote:
> Hi,
>
> There are a number of ports that seem to have their own preferential flavour
> of python, and some for example want to install python27 and python36 in the
> same place, and it's a pain when using portupgrade or similar tools.
Hi,
There are a number of ports that seem to have their own preferential
flavour of python, and some for example want to install python27 and
python36 in the same place, and it's a pain when using portupgrade or
similar tools.
I have this in my /etc/make.conf:
DEFAULT_VERSIONS+= python=2.7
Don't worry Steffen. Python won't be a build requirement for FreeBSD even
after Eric's patch. His Python script will only need to be run whenever
IANA updates its database, and the results will be checked into source
control. So for a normal user, there is no change to "make buildworld &&
make
Eric van Gyzen wrote in <59cd421e-f5d4-855a-83ec-65726f792...@vangyzen.net>:
|On 9/10/18 12:04 PM, Eric van Gyzen wrote:
|> Would anyone like to review this change to generate /etc/services from
|> the IANA registry?
|>
|> https://reviews.freebsd.org/D17106
|
|If that review made
On Mon, Sep 10, 2018 at 5:55 PM Mikaël Urankar
wrote:
> 2018-09-10 17:45 GMT+02:00 Andreas Nilsson :
>
>> Hello,
>>
>> I have for about a week been trying to get new (base)packages built. make
>> buildworld/buildkernel works as expected, however make packages has been
>> failing:
>>
>> ===>
I prefer releng, rather than stable, to make it default.
Binary releases requiring reproducible builds are built from
release and releng branches.
On Mon, 10 Sep 2018 10:56:14 -0400
Ed Maste wrote:
> The FreeBSD base system is a reproducible build[1] with a minor
> exception: the build
Submitting this here as I believe this may be best place to ask the question as
I use poudriere to test ports before sending patches
I am on 12 current. If I’m building a port that can use either py27 or py36 on
an non x86based system the py27 works fine on all my jails. If I test with py36
failed; see the
output of the test for details [0.150s]
===> Summary
Results read from /root/.kyua/store/results.usr_tests.20180911-070147-413583.db
Test cases: 7301 total, 212 skipped, 37 expected failures, 116 broken, 14 failed
Total time: 6688.125s
I'll note that the console reported over
Hi,
I am really excited to see that @rrs from Netflix is adding TCP RACK
and High Precision Timer System to the kernel, so I built a kernel
(r338543) and ran some test.
I used the following kernel config, as suggested in commit rS334804.
makeoptions WITH_EXTRA_TCP_STACKS=1
options TCPHPTS
On 9/10/18 8:26 PM, Mark Johnston wrote:
Hi,
Support for boot-time loading of Intel microcode updates has landed in
the kernel in r337715, and in the sysutils/devcpu-data port as of 1.20.
Thanks for your work.
Altough I cannot test it yet, I appreciate it.
Just one question: what about AMD?
28 matches
Mail list logo
