[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 generating the needed kernel options from the
current kernel config file.

-- 
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 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/msg138326.html

So I built drm-fbsd12.0-kmod-4.16.g20191024 via ports as a package (as well as
gpu-firmware-kmod-g20191015), then installed that package to get it working on
12.1-RC2 (needed because I'm building a Kodi box and need EVDEV for working
bluetooth mouse/keyboard via a mini keyboard device).  Before I rebuilt my
kernel w/o MAXCPU, it'd crash virtually the exact same way.  Just a slight
difference in the stack trace where after the call to
"intel_dp_init_connector", there's a call to "intel_edp_panel_vdd_sanitize",
then the call to "linux_queue_delayed_work_on", which goes on to trigger the
panic.

After rebuilding the 12.1-RC2 kernel and commenting out MAXCPU, it works fine
w/ i915kms.ko from the rebuilt drm-fbsd12.0-kmod package.  Even got Kodi up and
working (just working on sound output now).

-- 
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 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
   |loading module on ustom |loading module on custom
   |kernel w/ MAXCPU < 256  |kernel w/ MAXCPU < 256
   |(Invalid CPU in callout |(Invalid CPU in callout
   |256)|256)

-- 
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 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
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: darks...@darkbsd.org

I was running pf with the following line :

set skip on lo

Replacing it to :

set skip on lo0

And then reloading configuration with the following command ends up causing a
segmentation fault and a core dump :

# pfctl -f /etc/pf.conf

The core dump reveals it occured in strncmp() but pfctl did not provide the
base symbols so I can't be sure yet of what is going on.

#0  0x00080048c1d5 in strncmp () from /lib/libc.so.7
(gdb) bt
#0  0x00080048c1d5 in strncmp () from /lib/libc.so.7
#1  0x0021d7f0 in ?? ()
#2  0x00220c6a in ?? ()
#3  0x00222cbb in ?? ()
#4  0x0021d11b in ?? ()
#5  0x00080026d000 in ?? ()
#6  0x in ?? ()

It should also be noted that re-trying the command right after this works, this
time. Also, for some reason, I had to run pfctl twice to have traffic on the
loopback interface processed properly. (This would prove to be nasty because
DNS queries and traffic between jails would end up blocked...)

As a workaround, I have now removed "set skip on lo" and gone for "pass quick
on lo0 no state". This has mitigated both issues (the pf segfault when
rewriting pf.conf between lo and lo0, and traffic to lo0 being blocked)

-- 
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 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-RELEASE|CURRENT

-- 
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 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=edit
Add SSDP to services

Tested with: services_mkdb -o /tmp/services.13-CURRENT.db
~/src_current/usr.sbin/services_mkdb/services && echo "All good!"

-- 
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 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,
   ||hsela...@freebsd.org
 Status|New |Open
Version|12.1-RELEASE|12.0-RELEASE
  Flags||mfc-stable11?,
   ||mfc-stable12?
   Keywords||crash, needs-qa
   Severity|Affects Only Me |Affects Some People
Summary|kernel panic on loading of  |i915kms: Kernel panic
   |i915kms.ko if custom kernel |loading module on ustom
   |w/ MAXCPU < 256 |kernel w/ MAXCPU < 256
   ||(Invalid CPU in callout
   ||256)

--- Comment #1 from Kubilay Kocak  ---
Thank you for the report Joshua

Is the issue also reproducible with drm-kmod from ports?

See 12.0-RELEASE release notes [1]:

https://www.freebsd.org/releases/12.0R/relnotes.html#hardware-graphics

-- 
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 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
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: ku...@gentoo.org

Discovered that in both 12.0-RELEASE-p11 and 12.1-RC2-p0, on an Intel NUC8i5BEH
with Intel Iris Graphics, if one is running a custom kernel where "options
MAXCPU" is a value lower than the default of 256, loading i915kms.ko on boot
(via kld_list in /etc/rc.conf), the system will panic.  Partial bootlog is
below, manually transcribed from an image I took of the screen:

Loading kernel modules:
drmn0:  on vgapci0
vgapci0: child drmn0 requested pci_enable_io
vgapci0: child drmn0 requested pci_enable_io
<5>[drm] Unable to create a private tmpfs mount, hugepage support will be
disabled(-19).
<6>[drm] Found 128MB of eDRAM
Failed to add WC MTRR for [0x8000-0x8fff]: -22; performance may
suffer<6>[drm] Got stolen memory base 0x7c00, size 0x400
<6>[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
<6>[drm] Driver supports precise vblank timestap query.
<6>[drm] Connector eDP-1: get mode from tunables:
<6>[drm]   - kern.vt.fb.modes.eDP-1
<6>[drm]   - kern.vt.fb.default_mode
panic: Invalid CPU in callout 256
cpuid = 2
time = 1572817693
KDB: stack backtrace:
#0 0x8089cc47 at kdb_backtrace+0x67
#1 0x80850276 at vpanic+0x136
#2 0x80850133 at panic+0x43
#3 0x8086ad9a at callout_reset_sbt_on+0x36a
#4 0x825c3dcb at linux_queue_delayed_work_on+0x1db
#5 0x8249749b at intel_dp_init_connector+0x8bb
#6 0x82471195 at intel_ddi_init+0x365
#7 0x82484a88 at intel_modeset_init+0x1038
#8 0x82424b49 at i915_driver_load+0x14f9
#9 0x825be7d2 at linux_pci_attach+0x432
#10 0x8088b021 at device_attach+0x3e1
#11 0x8088d478 at bus_generic_driver_added+0xa8
#12 0x8088933a at devclass_driver_added+0x7a
#13 0x8088929a at devclass_add_driver+0x16a
#14 0x825bdf86 at _linux_pci_register_driver+0xf6
#15 0x8244f7fe at i915kms_evh+0x2e
#16 0x8082f3a4 at module_register_init+0xa4
#17 0x8082208f at linker_load_module+0xb3f

Workaround for now is to remove any change to MAXCPU from the custom kernel
config, or boot with the GENERIC kernel.

-- 
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 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 are any remaining concerns it looks like this can be resolved?

-- 
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 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 consists of "nested exception on signal stack" messages. Only seriously
affects Steam, although that message can also be seen on Wine environment
(wineserver & friends) shutdown, since one of the service applications dies
with it.

> stacktrace
It's Wine. No stacktraces for you. No debugger as well.

> emulators/i386-wine-devel (self-built in poudriere) works fine on 
> 13.0-CURRENT amd64.
I'm using a completely custom package set
(https://github.com/shkhln/freebsd-lib32-companion-ports).
i386-wine-devel-4.0.r1_1,1 package indeed doesn't have this issue.

-- 
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 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
   |blockers|potential
   ||blockers/post-release EN
   ||candidates

-- 
You are receiving this mail because:
You are on the CC list 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 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
   |potential   |post-release EN candidates
   |blockers/post-release EN|
   |candidates  |

-- 
You are receiving this mail because:
You are on the CC list 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"


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 obsolete releases.

Status  |Bug Id | Description
+---+---
In Progress |221973 | cam iosched: BIO_ZONE commands probably shouldn't 
In Progress |221974 | cam iosched: The iops limiter should enforce limi 
New |197876 | [devfs] an error in devfs leads to data loss and  
New |198797 | [PATCH] Added an option to install BSDstats to bs 
New |202362 | ntp: restore refclocks selection (10.2-RELEASE re 
New |202740 | vi/ex string substitution problem when there is m 
New |204097 | witness_initialize() does not perform bound check 
New |206336 | [patch] usr.sbin/freebsd-update allow proxy confi 
New |209213 | UEFI Loader shows only black screen with Nvidia G 
New |210804 | installerconfig - using ZFS create in custom scri 
New |223470 | freebsd-update: Cannot identify running kernel (/ 
New |224436 | vt: CONS_CLRHIST (vidcontrol -C) not implemented  
New |230620 | "install -d" issue
New |235085 | [PATCH] Option to make rc.d/sysctl more verbose ( 
Open| 71667 | [patch] cleanup of the usr.sbin/bootparamd code   
Open|182466 | [headers] [patch] make  self-contained  
Open|183618 | [panic] Dell PowerEdge R620 -- PERC H710 Mini (mf 
Open|187015 | agpgart: Panic make_dev_credv: bad si_name (error 
Open|194925 | [pf] [ifconfig] interface group keywords do not w 
Open|197921 | scheduler: Allow non-migratable threads to bind t 
Open|206528 | Emulex LPe 16002 FC HBA Not Recognized by oce(4)  
Open|207248 | [patch] daemon(8): Add option to redirect stdout  
Open|207940 | stand/efi/boot1: Add boot partition selection 
Open|212608 | sockstat(1) and lsof(8) can not identity the owne 
Open|220246 | syslogd does not send RFC3164-conformant messages 
Open|221305 | Mouse cursor loss when moving cursor while loadin 
Open|221550 | kern.bootfile returns only /kernel on mips64 (ERL 
Open|221854 | makefs: Reject UFS labels that are too long to fi 
Open|222632 | connect(2) not available in capability mode   
Open|226893 | freebsd-update: Support patchlevel argument for f 
Open|231810 | [build] release always fails with "mkimg: partiti 
Open|233578 | Unprivileged local user can prevent other users l 
Open|233988 | freebsd-update: Improve progress output on termin 
Open|236718 | system panics with message: vm_fault_hold: fault  
Open|237271 | Radeon video card no longer works on 12-STABLE (a 
Open|237287 | moused(8) ignores button release events in virtua 
Open|237924 | Possible infinite loop in function empty_aux_buff 
Open|237981 | cxgb(4): Driver doesn't work with latest (7.12) C 
Open|238183 | cam/scsi/scsi_sa.c: warnings issued by static ana 
Open|238486 | Possible buffer overflow bug in sc_allocate_keybo 
Open|238550 | Touchpad (via SMBus) not working: Synaptics (SYN1 
Open|238638 | mfi: Remove unnecessary pointer printing in mfi.c 
Open|238837 | init: Remove P_SYSTEM flag from PID 1 to allow ea 
Open|239976 | Integer Overflow: ping(8) option "-s", bypass the 
Open|239977 | Integer Overflow: ping(8) option "-G" and "-g", b 
Open|239978 | Integer Overflow: ping(8) option "-h", bypass the 
Open|240485 | ig4: Add Cannon Lake LP and H I2C Controller IDs  
Open|240572 | libefi: FreeBSD cannot boot with U-Boot patch efi 
New |230955 | [patch] Some speedup mergemaster  

49 problems total for which you should take action.
___
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 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 support

  That is done with re-execution of controller initialization procedure
  from resume handler.

  PR:   238037

Changes:
  head/sys/dev/ichiic/ig4_acpi.c
  head/sys/dev/ichiic/ig4_iic.c
  head/sys/dev/ichiic/ig4_pci.c
  head/sys/dev/ichiic/ig4_var.h
  head/sys/dev/iicbus/iicbus.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 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 CannonLake controllers

  They are clocked at 216MHz rate, much higher than previous models.

  PR:   240485
  Submitted by: Neel Chauhan 

Changes:
  head/sys/dev/ichiic/ig4_iic.c
  head/sys/dev/ichiic/ig4_pci.c
  head/sys/dev/ichiic/ig4_reg.h
  head/sys/dev/ichiic/ig4_var.h

-- 
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 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 Ed Maste  ---
Could not reproduce on ref12-amd64.freebsd.org either; perhaps this was fixed
on stable/12 after 12.0 released.

-- 
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 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 non-UTF8 charset I know of.

-- 
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 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
   |ENOMEM but silently |ENOMEM but silently
   |truncate return data|truncate returned data

-- 
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 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 crashes for me in a
> USR1 signal handler in dlls/ntdll/signal_i386.c, I had to comment
> the entire thing out

Maybe file a separate bug with more details e.g., sample program, wine output,
stacktrace. emulators/i386-wine-devel (self-built in poudriere) works fine on
13.0-CURRENT amd64.

-- 
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 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
HAIRCLIPPER
root@vas:~ # ls /media
da0 da0p2   da0s1   HAIRCLIPPER
root@vas:~ #

-- 
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 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 from Mark Linimon  ---
(In reply to vermaden from comment #18)

I understand that you are frustrated but please understand that all the desktop
effort is done by volunteers.  Their work is unrewarding enough without being
cussed at.  It's not appropriate.

-- 
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 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 #284 from Victor B. Kuntz  ---
Thanks For Sharing i hope This type Of Post I Reach on You Web Page.




Regards:https://instapotbuy.com

-- 
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 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
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: v...@sibptus.ru

When automounting removable media via the -media map, there is no way to
specify filesystem permissions to the subdirectories of /media other than the
default "drwxr-xr-x root:wheel" which prevents unprivileged users from writing
to the removable flash drives etc. Permissions of the /media directory are not
being inherited.

-- 
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 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
using the FreeBSD 11.2 LSI mps driver. 12.1 brings in many updates to the 12.0
mps driver, hopefully those address these problems; will test once its
released.

/Sharad

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