date:20190827

Re: FreeBSD 12 Xorg vs X11SSH-F / AST

2019-08-27 Thread O'Connor, Daniel

> On 27 Aug 2019, at 13:45, O'Connor, Daniel  wrote:
> 
> Although I could set uncacheable (no difference).
> 
> Next stop will be obscure BIOS settings I suppose.

I couldn't find anything useful there.

I realised that my scfb failure was because I am booting BIOS rather than UEFI 
but I will have to reinstall before I can fix that.

There was a thread about a performance regression in Linux 
(https://ubuntuforums.org/showthread.php?t=2399941) but that applies to KMS.. I 
checked the drm-kmod port but there is no ASPEED driver there.

--
Daniel O'Connor
"The nice thing about standards is that there
are so many of them to choose from."
 -- Andrew Tanenbaum

___
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"

Re: svn commit: r351246 - in stable: 11/sys/opencrypto 12/sys/opencrypto

2019-08-27 Thread John Baldwin

On 8/26/19 5:25 PM, John Baldwin wrote:
> On 8/26/19 1:59 PM, mike tancsa wrote:
>> On 8/22/2019 6:51 PM, John Baldwin wrote:
>>> On 8/21/19 5:47 PM, Mike Tancsa wrote:
 On 8/21/2019 6:38 PM, John Baldwin wrote:
> On 8/21/19 9:08 AM, mike tancsa wrote:
>> On 8/21/2019 12:00 PM, John Baldwin wrote:
>>> dtrace -n 'fbt::_gone_in:entry { @counts[curthread->td_proc->p_comm] = 
>>> count()'
>> Thanks, I am not familiar with dtrace at all. This command gives a
>> syntax error
>>
>> 0(cage)# dtrace -n 'fbt::_gone_in:entry {
>> @counts[curthread->td_proc->p_comm] = count()'
>> dtrace: invalid probe specifier fbt::_gone_in:entry {
>> @counts[curthread->td_proc->p_comm] = count(): syntax error near end of
>> input
>> 1(cage)#
> Oops, I forgot the closing }.  First, do "dtrace -l | grep _gone_in" to 
> make
> sure dtrace is loaded.  You should see something like this:
>
> # dtrace -l | grep _gone_in
> 87003fbtkernel  _gone_in entry
> 87004fbtkernel  _gone_in 
> return
> 98682fbtkernel  _gone_in_dev entry
> 98683fbtkernel  _gone_in_dev 
> return
>
> Then this should work:
>
> # dtrace -n 'fbt::_gone_in:entry { @counts[curthread->td_proc->p_comm] = 
> count() }'
> dtrace: description 'fbt::_gone_in:entry ' matched 1 probe
>
 Thanks!

 #  dtrace -l | grep _gone_in
 15632    fbt    kernel  _gone_in entry
 22693    fbt    kernel  _gone_in_dev entry

 # dtrace -n 'fbt::_gone_in:entry { @counts[curthread->td_proc->p_comm] =
 count() }'
 dtrace: description 'fbt::_gone_in:entry ' matched 1 probe

 However, It doesnt show anything after that even as I get the
 deprecation messages in dmesg
>>> Can you hit Ctrl-C after seeing some of the messages?  This trace won't
>>> show any results until you exit dtrace.
>>
>> Hi,
>>
>>     I am still having problems tracking it down via dtrace, but I am
>> able to create the problem on demand on sshd.  Whats odd is that if I
>> restrict the list of ciphers in sshd and even specify something like
>> aes-128 on the client, I still get warnings on the server.
>>
>> e.g from a client,
>>
>> % ssh -c aes128-cbc console1 uptime
>>  4:53PM  up  1:02, 3 users, load averages: 0.04, 0.08, 0.08
>>
>> The server shows
> 
> Ok, I was able to reproduce this on an 11.x VM.  It appears to only
> be something that the crypto engine in OpenSSL 1.0.x does (1.1.1 used
> in 12.0 and later has a rewritten /dev/crypto engine).
> 
> I'll see if I can find a way to tone down the warning.  Maybe if
> sshd is only creating sessions and not using them I can restrict
> it to warning the first time a session tries to perform an operation
> using a deprecated algorithm.  (There are separate ioctls for
> creating a sessions vs doing actual crypto ops and the warning is
> in the session creation currently.)

I've committed a fix to head and will MFC it in a few days.  Thanks for tracking
this down!

-- 
John Baldwin
___
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"

FreeBSD CI Weekly Report 2019-08-25

2019-08-27 Thread Li-Wen Hsu

(Please send the followup to freebsd-testing@ and note Reply-To is set.)

FreeBSD CI Weekly Report 2019-08-25
===

Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-08-19 to 2019-08-25.

During this period, we have:

* 2262 builds (83% (-10.3) passed, 17% (+10.3) failed) were executed on
  aarch64, amd64, armv6, armv7, i386, mips, mips64, powerpc, powerpc64,
  powerpcspe, riscv64, sparc64 architectures for head, stable/12, stable/11
  branches.
* 403 test runs (45.2% (-18.1) passed, 48.8% (+14.1) unstable, 6% (+4)
  exception) were executed on amd64, i386, riscv64 architectures for head,
  stable/12, stable/11 branches.
* 38 doc builds (100% (0) passed)

Test case status (on 2019-08-25 23:59):
| Branch/Architecture | Total  | Pass   | Fail| Skipped  |
| --- | -- | -- | --- |  |
| head/amd64  | 7533 (+22) | 7463 (+17) | 0 (-2)  | 70 (+7)  |
| head/i386   | 7531 (+22) | 7455 (+18) | 0 (-2)  | 74 (+4)  |
| 12-STABLE/amd64 | 7392 (0)   | 7345 (+4)  | 0 (-2)  | 47 (-2)  |
| 12-STABLE/i386  | 7390 (0)   | 7336 (+4)  | 0 (-2)  | 54 (-2)  |
| 11-STABLE/amd64 | 6845 (0)   | 6801 (+7)  | 0 (0)   | 44 (-7)  |
| 11-STABLE/i386  | 6843 (0)   | 6763 (+7)  | 34 (0)  | 46 (-7)  |

(The statistics from experimental jobs are omitted)

If any of the issues found by CI are in your area of interest or expertise
please investigate the PRs listed below.

The latest web version of this report is available at
https://hackmd.io/s/HkcTCgnVB and archive is available at
http://hackfoldr.org/freebsd-ci-report/, any help is welcome.

## News
  
* [FCP 20190401-ci_policy: CI policy
](https://github.com/freebsd/fcp/blob/master/fcp-20190401-ci_policy.md) is in 
"feedback" state, please check and provide comments.

* Per imp@ suggested [timeline of gcc 4.2.1 
removal](https://lists.freebsd.org/pipermail/freebsd-arch/2019-August/019674.html):
* -Werror has been turned off for gcc 4.2.1 in
  [r351429](https://svnweb.freebsd.org/changeset/base/351429) and
  [r351430](https://svnweb.freebsd.org/changeset/base/351430)
* power*-build has been fixed in 
[r351485](https://svnweb.freebsd.org/changeset/base/351485)
* amd64-gcc build still need fix, patch is being discussed in
  https://reviews.freebsd.org/D21418

* Some pf tests failing on i386 which may be related to bpf, need more help:
* https://lists.freebsd.org/pipermail/freebsd-testing/2019-June/001933.html
* https://lists.freebsd.org/pipermail/freebsd-testing/2019-June/001934.html

## Fixed Tests

* https://ci.freebsd.org/job/FreeBSD-head-amd64-test/12237/
* https://ci.freebsd.org/job/FreeBSD-head-i386-test/6383/
* sys.acl.00.main
* sys.acl.02.main
  Fixed by update package to perl5.30
* sys.netpfil.pf.forward.v4
* sys.netpfil.pf.icmp.cve_2019_5598
  Due to [r351212](https://svnweb.freebsd.org/changeset/base/351212) 
changed options of ping6(8),
  fixed in [r351391](https://svnweb.freebsd.org/changeset/base/351391)

## Failing Tests

* https://ci.freebsd.org/job/FreeBSD-stable-11-i386-test/
* local.kyua.* (31 cases)
* local.lutok.* (3 cases)

## Failing and Flaky Tests (from experimental jobs)

* https://ci.freebsd.org/job/FreeBSD-head-amd64-dtrace_test/
* Flakey test case: common.misc.t_dtrace_contrib.tst_dynopt_d
  https://bugs.freebsd.org/237641

* https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/
* There are ~60 failing cases, including flakey ones, see 
https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs/lastCompletedBuild/testReport/
 for more details

## Disabled Tests

* lib.libc.sys.mmap_test.mmap_truncate_signal
  https://bugs.freebsd.org/211924
* sys.fs.tmpfs.mount_test.large
  https://bugs.freebsd.org/212862
* sys.fs.tmpfs.link_test.kqueue
  https://bugs.freebsd.org/213662
* sys.kqueue.libkqueue.kqueue_test.main
  https://bugs.freebsd.org/233586
* sys.kern.ptrace_test.ptrace__PT_KILL_competing_stop
  https://bugs.freebsd.org/220841
* usr.bin.procstat.procstat_test.command_loogle.com/ine_arguments
  https://bugs.freebsd.org/233587
* usr.bin.procstat.procstat_test.environment
  https://bugs.freebsd.org/233588
* lib.libc.regex.exhaust_test.regcomp_too_big (i386 only)
  https://bugs.freebsd.org/237450
* sys.netinet.socket_afinet.socket_afinet_bind_zero (new)
  https://bugs.freebsd.org/238781
* sys.netpfil.pf.names.names
* sys.netpfil.pf.synproxy.synproxy
  https://bugs.freebsd.org/238870
* sys.kern.ptrace_test.ptrace__follow_fork_child_detached_unrelated_debugger 
  https://bugs.freebsd.org/239292
* sys.netpfil.pf.forward.v4 (i386 only)
* sys.netpfil.pf.forward.v6 (i386 only)
* sys.netpfil.pf.set_tos.v4 (i386 only)
  https://bugs.freebsd.org/239380
* sys.kern.ptrace_test.ptrace__follow_fork_both_attached_unrelated_debugger 
  https://bugs.freebsd.org/239397
* sys.kern.ptrace_test.ptrace__parent_sees_exit_after_child_debugger
  https:/

Re: FreeBSD 12 Xorg vs X11SSH-F / AST

Re: svn commit: r351246 - in stable: 11/sys/opencrypto 12/sys/opencrypto

FreeBSD CI Weekly Report 2019-08-25

3 matches

Site Navigation

Mail list logo

Footer information