[Bug 224496] mpr and mps drivers seems to have issues with large seagate drives

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224496 --- Comment #20 from free...@diyit.org --- (In reply to Paul Thornton from comment #19) Thanks for sharing Paul. I took a slightly different approach. I have been running stable for a few months now with a FreeBSD 12.0-RELEASE kernel but us

[Bug 241684] autofs: no way to have permissions other than 755 for automounted media

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241684 Bug ID: 241684 Summary: autofs: no way to have permissions other than 755 for automounted media Product: Base System Version: 11.3-RELEASE Hardware: Any

[Bug 219399] System panics after several hours of 14-threads-compilation orgies using poudriere on AMD Ryzen...

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399 Victor B. Kuntz changed: What|Removed |Added CC||saamhoc...@gmail.com --- Comment

[Bug 233400] 12.0-RC1 - FreeBSD 12.x Breaks WINE

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233400 Mark Linimon changed: What|Removed |Added CC||lini...@freebsd.org --- Comment #20

[Bug 241531] autofs: stale entries remain in /media, "automount -c" does not remove them

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241531 --- Comment #2 from Victor Sudakov --- Really, why does it accumulate all that stale stuff? root@vas:~ # automount -cv |& grep flush automount: flushing autofs caches automount: flushing /media root@vas:~ # /etc/autofs/special_media HAIRCL

[Bug 233400] 12.0-RC1 - FreeBSD 12.x Breaks WINE

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233400 --- Comment #21 from Jan Beich --- Success story tends to be better on -CURRENT where regressions are easier to catch and developers haven't moved on. (In reply to Alex S from comment #19) > I recently upgraded to 12.1 and found that Wine

[Bug 240573] sysctl() does not return ENOMEM but silently truncate returned data

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240573 rozhuk...@gmail.com changed: What|Removed |Added Summary|sysctl() does not return|sysctl() does not return

[Bug 241679] /usr/bin/sort fails if UTF-8 input is received from stdin

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241679 --- Comment #1 from Conrad Meyer --- I can't reproduce the issue on 13-CURRENT with the following environment: LANG=en_US.UTF-8 I also cannot reproduce it on 13-CURRENT with unset LANG or LANG=C or C.US-ASCII, or LC_CTYPE set to any weird

[Bug 241679] /usr/bin/sort fails if UTF-8 input is received from stdin

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241679 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #2 from

[Bug 240485] ig4: Add Cannon Lake LP and H I2C Controller IDs

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240485 --- Comment #17 from commit-h...@freebsd.org --- A commit references this bug: Author: wulf Date: Sun Nov 3 21:16:07 UTC 2019 New revision: 354320 URL: https://svnweb.freebsd.org/changeset/base/354320 Log: [ig4] Add support for CannonLa

[Bug 238037] [PATCH] Implement ig4 suspend/resume

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238037 --- Comment #20 from commit-h...@freebsd.org --- A commit references this bug: Author: wulf Date: Sun Nov 3 21:00:57 UTC 2019 New revision: 354308 URL: https://svnweb.freebsd.org/changeset/base/354308 Log: [ig4] Add suspend/resume suppo

Problem reports for b...@freebsd.org that need special attention

2019-11-03 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 240700] [META] FreeBSD 12.1-RELEASE post-release EN candidates

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240700 Glen Barber changed: What|Removed |Added Summary|[META] FreeBSD 12.1-RELEASE |[META] FreeBSD 12.1-RELEASE

[Bug 240700] [META] FreeBSD 12.1-RELEASE potential blockers/post-release EN candidates

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240700 Glen Barber changed: What|Removed |Added Summary|[META] FreeBSD 12.1-RELEASE |[META] FreeBSD 12.1-RELEASE

[Bug 233400] 12.0-RC1 - FreeBSD 12.x Breaks WINE

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233400 --- Comment #22 from Alex S --- (In reply to Jan Beich from comment #21) > Maybe file a separate bug with more details e.g., sample program, wine output Let's not kid ourselves, then I would have to at least partially debug it. The output

[Bug 238037] [PATCH] Implement ig4 suspend/resume

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238037 --- Comment #21 from Austin Shafer --- It's great to see a commit pushing this through! I wish I could have had a machine to play around with this on, but I've been following the phabricator thread and the other ig4 commits. Unless there a

[Bug 241697] kernel panic on loading of i915kms.ko if custom kernel w/ MAXCPU < 256

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241697 Bug ID: 241697 Summary: kernel panic on loading of i915kms.ko if custom kernel w/ MAXCPU < 256 Product: Base System Version: 12.1-RELEASE Hardware: amd64

[Bug 241697] i915kms: Kernel panic loading module on ustom kernel w/ MAXCPU < 256 (Invalid CPU in callout 256)

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241697 Kubilay Kocak changed: What|Removed |Added CC||gleb...@freebsd.org,

[Bug 241573] 12.1-RC2 usr.sbin/services_mkdb/services doesn't include SSDP, despite that protocol being used (for UPnP)

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241573 --- Comment #1 from PauAmma --- Created attachment 208838 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=208838&action=edit Add SSDP to services Tested with: services_mkdb -o /tmp/services.13-CURRENT.db ~/src_current/usr.sbin/se

[Bug 241573] 12.1-RC2 usr.sbin/services_mkdb/services doesn't include SSDP, despite that protocol being used (for UPnP)

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241573 PauAmma changed: What|Removed |Added Keywords||feature, patch Version|12.1-R

[Bug 241698] pfctl segmentation fault, weird "set skip" behavior

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241698 Bug ID: 241698 Summary: pfctl segmentation fault, weird "set skip" behavior Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New

[Bug 241697] i915kms: Kernel panic loading module on custom kernel w/ MAXCPU < 256 (Invalid CPU in callout 256)

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241697 Joshua Kinard changed: What|Removed |Added Summary|i915kms: Kernel panic |i915kms: Kernel panic

[Bug 241697] i915kms: Kernel panic loading module on custom kernel w/ MAXCPU < 256 (Invalid CPU in callout 256)

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241697 --- Comment #2 from Joshua Kinard --- I believe it is. When I initially tested on 12.1-RC2, I followed this mailing list thread here, thinking this thread highlighted my problem: https://www.mail-archive.com/freebsd-stable@freebsd.org/msg1

[Bug 241697] i915kms: Kernel panic loading module on custom kernel w/ MAXCPU < 256 (Invalid CPU in callout 256)

2019-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241697 --- Comment #3 from Hans Petter Selasky --- I suspect the drm-kms modules need default values for some kernel parameters, because when building these we don't use the config file used by the kernel. This might be possible to fix, by generat