[Bug 214163] kernel build fails: undefined reference to `memset'

2016-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214163

o...@zaplinski.de changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |Not A Bug

--- Comment #1 from o...@zaplinski.de ---
My fault, I had WITHOUT_FORTH in src.conf

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 214162] kernel build fails because of missing libstand.a

2016-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214162

o...@zaplinski.de changed:

   What|Removed |Added

 Resolution|--- |Not A Bug
 Status|New |Closed

--- Comment #1 from o...@zaplinski.de ---
My fault, I had WITHOUT_FORTH in src.conf

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 209441] SSHd in FreeBSD 10.3 complains about PrintLastLog

2016-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209441

elof...@hotmail.com changed:

   What|Removed |Added

 CC||elof...@hotmail.com

--- Comment #1 from elof...@hotmail.com ---
I just upgraded a 10.1 machine to 10.3 and got exactly the same.

2016-11-04 15:28:02 +01:00 foobar sshd[3899]: rexec line 12: Unsupported option
PrintLastLog

What gives?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 214217] Nvidia NVS 300 support

2016-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214217

Bug ID: 214217
   Summary: Nvidia NVS 300 support
   Product: Base System
   Version: 11.0-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: kp...@protonmail.com
CC: freebsd-am...@freebsd.org
CC: freebsd-am...@freebsd.org

Hello.

I have Nvidia NVS 300 video card, but when I'm trying to start Xorg it fails to
initialize and I get following error: "failed shmoo sddr3 link training" in the
log file.
After googling a bit I've found following link:

https://devtalk.nvidia.com/default/topic/598926/freebsd/freebsd-9-1-failed-shmoo-sddr3-link-training-error/

It's been stated there that FreeBSD kernel misses a hardware bug workaround for
NVS 300. Is it possible to implement this workaraund?
I would be very disapointing to have a new videocard with broken support, not
being able to use it.

Best regards,
Sergey.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 209441] SSHd in FreeBSD 10.3 complains about PrintLastLog

2016-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209441

Jason Mader  changed:

   What|Removed |Added

 CC||jasonma...@gmail.com

--- Comment #2 from Jason Mader  ---
PrintLastLog is also in FreeBSD 11.0-RELEASE sshd_config and man page

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 214226] sshd RekeyLimit

2016-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214226

Bug ID: 214226
   Summary: sshd RekeyLimit
   Product: Base System
   Version: 11.0-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: conf
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: jasonma...@gmail.com
CC: freebsd-am...@freebsd.org
CC: freebsd-am...@freebsd.org

sshd_config keyword RekeyLimit does not appear to change the maximum amount of
data. The debug message is always the same below. And testing transferring 3GiB
show the same rekey intervals whether the value was 1G or 4G. Cipher is
chacha20-poly1...@openssh.com

debug1: rekey after 134217728 blocks

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 211713] NVME controller failure: resetting

2016-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211713

frederic.las...@live.at changed:

   What|Removed |Added

 CC||frederic.las...@live.at

--- Comment #4 from frederic.las...@live.at ---
I've got the same problem with a Samsung SSD SM961 256GB and FreeBSD 11.0. The
SSD works fine with Ubuntu and Windows.

my equipment:
Xeon E3-1245v5
Gigabyte GA-X170-Extreme ECC
2x Kingston KVR21E15D8K2/16I = 32GB
Samsung SSD SM961 256GB, M.2 (MZVPW256HEGL-0)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 203349] [META] FreeBSD Foundation sponsored project dependencies for FreeBSD 11.1

2016-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203349

Ed Maste  changed:

   What|Removed |Added

Summary|[META] FreeBSD Foundation   |[META] FreeBSD Foundation
   |sponsored project   |sponsored project
   |dependencies for FreeBSD|dependencies for FreeBSD
   |11.0|11.1

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 213474] sed behavior change with a/i/c operands.

2016-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213474

--- Comment #5 from commit-h...@freebsd.org ---
A commit references this bug:

Author: pfg
Date: Fri Nov  4 20:49:59 UTC 2016
New revision: 308314
URL: https://svnweb.freebsd.org/changeset/base/308314

Log:
  sed(1): add LEGACY_BSDSED_COMPAT compile-time flag.

  In r297602, which included a __FreeBSD_version bump to 1100105, we changed
  sed 'i' and 'a' from discarding whitespaces to conform with what GNU and
  sysvish sed do.

  There are arguments in favor of keeping the old behavior but the new
  behavior is also useful for migration purposes. It seems important to at
  least consider the case of developers depending on the previous behavior,
  so add a CFLAG to enable the old behaviour.

  PR:   213474
  MFC after:5 days

Changes:
  head/usr.bin/sed/compile.c

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 213922] crafted data could cause qsort to exhaust stack space

2016-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213922

Pedro F. Giffuni  changed:

   What|Removed |Added

 CC||a...@freebsd.org,
   ||p...@freebsd.org

--- Comment #2 from Pedro F. Giffuni  ---
(In reply to jhoward from comment #1)

Hi;

I am CC'ing Andrey Chernov as he has done changes in qsort(3).

The change is interesting, but it has to be benchmarked first. Perhaps you can
try the tests in lib/libc/tests/stdlib/ and see how the compare to the existing
code?
FWIW, ministat(1) is welcome too ;).

Also, we generally don't touch the stuff in contrib until the changes are
reviewed by upstream maintainers.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"