Re: nmount, mountd drops high order MNT_xx flags during a mount update

2015-05-06 Thread Doug Rabson
You could add a single integer-valued vfsopt which holds the high-order bits of f_flags? On 7 May 2015 at 02:10, Rick Macklem wrote: > David Boyd reported a problem to freebsd-current@ w.r.t. the > MNT_AUTOMOUNTED > flag getting cleared by mountd. > http://docs.FreeBSD.org/cgi/mid.cgi?14294772

Jenkins build is back to stable : FreeBSD_HEAD-tests2 #1011

2015-05-06 Thread jenkins-admin
See ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

nmount, mountd drops high order MNT_xx flags during a mount update

2015-05-06 Thread Rick Macklem
David Boyd reported a problem to freebsd-current@ w.r.t. the MNT_AUTOMOUNTED flag getting cleared by mountd. http://docs.FreeBSD.org/cgi/mid.cgi?1429477202.29812.38.camel I just took a look at this and it's kinda ugly... mountd acquires a list of mounts via getmntinfo() and then does an nmount()

Re: PCI PF memory decode disable when sizing VF BARs

2015-05-06 Thread Eric Badger
On 05/06/15 14:54, Ryan Stone wrote: On Wed, May 6, 2015 at 2:33 PM, John Baldwin > wrote: Ah, sorry, I didn't know you did it in the caller already. Perhaps then something more like your previous patch, but using the test you added here (PCIR_IS_IOV) inste

Jenkins build became unstable: FreeBSD_HEAD-tests2 #1010

2015-05-06 Thread jenkins-admin
See ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: PCI PF memory decode disable when sizing VF BARs

2015-05-06 Thread Eric Badger
On 05/06/15 13:33, John Baldwin wrote: On Wednesday, May 06, 2015 02:24:24 PM Ryan Stone wrote: On Wed, May 6, 2015 at 11:45 AM, John Baldwin wrote: There are some devices with BARs in non-standard locations. :( If there is a flag to just disable the VF bar decoding, then ideally we should j

Re: PCI PF memory decode disable when sizing VF BARs

2015-05-06 Thread John Baldwin
On Wednesday, May 06, 2015 02:24:24 PM Ryan Stone wrote: > On Wed, May 6, 2015 at 11:45 AM, John Baldwin wrote: > > > There are some devices with BARs in non-standard locations. :( If there is > > a flag to just disable the VF bar decoding, then ideally we should just be > > doing that and leavin

Re: PCI PF memory decode disable when sizing VF BARs

2015-05-06 Thread Ryan Stone
On Wed, May 6, 2015 at 11:45 AM, John Baldwin wrote: > There are some devices with BARs in non-standard locations. :( If there is > a flag to just disable the VF bar decoding, then ideally we should just be > doing that and leaving the global decoding flag alone while sizing the VF > BAR. > Disa

Re: PCI PF memory decode disable when sizing VF BARs

2015-05-06 Thread John Baldwin
On Tuesday, May 05, 2015 07:15:21 PM Ryan Stone wrote: > On Tue, May 5, 2015 at 9:17 AM, Eric Badger wrote: > > > Hi Ryan and -current, > > > > During IOV config, when setting up VF bars, several calls are made to > > 'pci_read_bar' (in sys/dev/pci/pci.c) in order to size VF BARs, which > > cause

vt: blank screen switching from X11 to console/vtty

2015-05-06 Thread O. Hartmann
Running a Fujitsu Celsius M740 Workstation with a nVidia Quadro NVS 315 GPU, most recent driver (346.16), UEFI boot, and FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r282520: Wed May 6 08:14:14 CEST 2015 amd64, switching from graphics terminal (X11), located at vty7 (xdm) to any console vty[0-6],