In order to boot USB reliably on recent laptop hardware (both my thinkpad and
XPS13 need this) you need to add the following to the installer images
loader.conf:
kern.cam.boot_delay="1"
kern.cam.scsi_delay="3000"
___
freebsd-current@freebsd.org
> On Jun 3, 2016, at 10:23 AM, Eric van Gyzen wrote:
>
> My buildworld just failed very early with a segfault from /usr/bin/ar:
>
>--
stage 1.1: legacy release compatibility shims
>-
Hi,
I've recently observed a hang in a multi-threaded process that had hit
an assertion failure and was attempting to dump core. One thread was
sleeping interruptibly on an advisory lock with TDF_SBDRY set (our
filesystem sets VFCF_SBDRY). SIGABRT caused the receipient thread to
suspend other thre
On 3 Jun, Don Lewis wrote:
> It looks like something changed in -CURRENT to break network
> connectivity to VirtualBox guests. This was last known to work with
> r299139 (May 6th) and is definitely broken with r301229. The VirtualBox
> port revisions are:
> virtualbox-ose-4.3.38_1
>
It looks like something changed in -CURRENT to break network
connectivity to VirtualBox guests. This was last known to work with
r299139 (May 6th) and is definitely broken with r301229. The VirtualBox
port revisions are:
virtualbox-ose-4.3.38_1
virtualbox-ose-kmod-4.3.38
It looks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
New FreeBSD development branch installation ISOs and virtual machine
disk images have been uploaded to the FTP mirrors.
As with any development branch, the installation snapshots are not
intended for use on production systems. We do, however, encou
On 6/1/2016 12:38 PM, Bryan Drewery wrote:
>> WITHOUT_CROSS_COMPILER=
> It's likely related to this flag. I'll look into it.
I've fixed this in r301287.
--
Regards,
Bryan Drewery
signature.asc
Description: OpenPGP digital signature
On 3 June 2016 at 11:27, Adrian Chadd wrote:
> That and the other NUMA stuff is something to address in -12.
And, I completely welcome continued development in NUMA scaling in
combination with discussion. The iterator changes I committed are a
more generic version of a patch people were applying
On 3 June 2016 at 10:55, Konstantin Belousov wrote:
> On Fri, Jun 03, 2016 at 11:29:13AM -0600, Alan Somers wrote:
>> On Fri, Jun 3, 2016 at 11:26 AM, Konstantin Belousov
>> wrote:
>> > On Fri, Jun 03, 2016 at 09:29:16AM -0600, Alan Somers wrote:
>> >> I notice that, with the exception of the VM_
On Fri, Jun 03, 2016 at 11:29:13AM -0600, Alan Somers wrote:
> On Fri, Jun 3, 2016 at 11:26 AM, Konstantin Belousov
> wrote:
> > On Fri, Jun 03, 2016 at 09:29:16AM -0600, Alan Somers wrote:
> >> I notice that, with the exception of the VM_PHYSSEG_MAX change, these
> >> patches never made it into h
On Fri, Jun 3, 2016 at 11:26 AM, Konstantin Belousov
wrote:
> On Fri, Jun 03, 2016 at 09:29:16AM -0600, Alan Somers wrote:
>> I notice that, with the exception of the VM_PHYSSEG_MAX change, these
>> patches never made it into head or ports. Are they unsuitable for low
>> core-count machines, or i
On Fri, Jun 03, 2016 at 09:29:16AM -0600, Alan Somers wrote:
> I notice that, with the exception of the VM_PHYSSEG_MAX change, these
> patches never made it into head or ports. Are they unsuitable for low
> core-count machines, or is there some other reason not to commit them?
> If not, what woul
My buildworld just failed very early with a segfault from /usr/bin/ar:
--
>>> stage 1.1: legacy release compatibility shims
--
...
--- libegacy.a ---
buil
On Fri, Jun 03, 2016 at 08:04:29AM -0700, Maxim Sobolev wrote:
> Konstantin,
>
> Thanks for taking your time looking into it and sorry for somewhat messy
> problem report. I've been trying to fix that problem all day yesterday
> thinking it's just application logic that is broken and indeed has be
> >>> A couple small steps have been taken toward eliminating the need for
> >>> this
> >>> hack: the addition of the "page size index" field to struct vm_page and
> >>> the
> >>> addition of a similarly named parameter to pmap_enter(). However, at
> >>> the
> >>> moment, the only ta
On 3 June 2016 at 12:49, Eric van Gyzen wrote:
> I'm running head from Tuesday (r301045). I just noticed that "ar" is
> missing the debuginfo for libarchive:
I discussed this with Eric off this thread, but for the sake of others
this is happening because WITH_DEBUG_FILES enables -g when building
I'm running head from Tuesday (r301045). I just noticed that "ar" is
missing the debuginfo for libarchive:
$ /usr/local/bin/gdb /usr/bin/ar
GNU gdb (GDB) 7.11 [GDB v7.11 for FreeBSD]
[...]
Reading symbols from /usr/bin/ar...Reading symbols from
/usr/lib/debug//usr/bin/ar.debug
On 3 June 2016 at 05:34, Kubiak, Patryk wrote:
> Hi ,
>
> I have question about mmap and /dev/mem in the FreeBSD 11. We found, that
> ours applications does not work correct in the 11 - there is a problem with
> mapping physical memory via mmap and /dev/mem device - we are receiving
> "Permissi
On Thu, Aug 14, 2014 at 12:19 PM, Alan Cox wrote:
> On 08/14/2014 10:47, John Baldwin wrote:
>> On Wednesday, August 13, 2014 1:00:22 pm Alan Cox wrote:
>>> On Tue, Aug 12, 2014 at 1:09 PM, John Baldwin wrote:
>>>
On Wednesday, July 16, 2014 1:52:45 pm Adrian Chadd wrote:
> Hi!
>
>>>
Konstantin,
Thanks for taking your time looking into it and sorry for somewhat messy
problem report. I've been trying to fix that problem all day yesterday
thinking it's just application logic that is broken and indeed has been
able to find some bigger issues that were obscuring this one. But it g
a. multiple cores.
b. makes no difference
c. yes, I believe so
kern.timecounter.tsc_shift: 1
kern.timecounter.smp_tsc_adjust: 0
kern.timecounter.smp_tsc: 1
kern.timecounter.invariant_tsc: 1
machdep.tsc_freq: 2658118740
machdep.disable_tsc_calibration: 0
machdep.disable_tsc: 0
d. no, single socket
Hi ,
I have question about mmap and /dev/mem in the FreeBSD 11. We found, that ours
applications does not work correct in the 11 - there is a problem with mapping
physical memory via mmap and /dev/mem device - we are receiving "Permission
Denied" error. Is there any important change in the new
Op 2016-06-03 om 06:16 schreef Maxim Sobolev:
4. If the answer for (3) is yes, then what is the method to disable using
TSC and use slower but possibly more reliable method?
sysctl kern.timecounter.choice lists the available timers.
sysctl kern.timecounter.hardware selects the timer. Changes ta
23 matches
Mail list logo
