On Fri, May 23, 2014 at 8:42 PM, Tim Bishop wrote:
> On Fri, May 23, 2014 at 08:07:03PM -0600, Alan Somers wrote:
>> On Fri, May 23, 2014 at 7:47 PM, Tim Bishop wrote:
>> > I have a new quad CPU system containing four of these processors:
>> >
>> > Intel(R) Xeon(R) CPU E7-4830 v2 @ 2.20GHz (2200.
On Fri, May 23, 2014 at 08:07:03PM -0600, Alan Somers wrote:
> On Fri, May 23, 2014 at 7:47 PM, Tim Bishop wrote:
> > I have a new quad CPU system containing four of these processors:
> >
> > Intel(R) Xeon(R) CPU E7-4830 v2 @ 2.20GHz (2200.05-MHz K8-class CPU)
> >
> > I've tried FreeBSD 10.0, stab
On Fri, May 23, 2014 at 7:47 PM, Tim Bishop wrote:
> I have a new quad CPU system containing four of these processors:
>
> Intel(R) Xeon(R) CPU E7-4830 v2 @ 2.20GHz (2200.05-MHz K8-class CPU)
>
> I've tried FreeBSD 10.0, stable/10 and head, but all of them only detect
> a maximum of 64 "CPUs". The
(Dropped the cross-posting, which *is* frowned upon)
While I do very much appreciate this work being done, and I agree we should
have it in the tree, I would really prefer it opt-in rather opt-out, at least
initially.
I know this may very well be the subject of a bikeshed of historical
proport
On May 23, 2014 07:53 PM +, Wojciech A. Koszek wrote:
> On Wed, May 14, 2014 at 09:58:52AM -0400, Shawn Webb wrote:
> > Hey All,
> >
> > [NOTE: crossposting between freebsd-current@, freebsd-security@, and
> > freebsd-stable@. Please forgive me if crossposting is frowned upon.]
> >
> > Addres
On 5/14/14, Shawn Webb wrote:
> Hey All,
>
> [NOTE: crossposting between freebsd-current@, freebsd-security@, and
> freebsd-stable@. Please forgive me if crossposting is frowned upon.]
>
> Address Space Layout Randomization, or ASLR for short, is an exploit
> mitigation technology. It helps secure
On Friday, May 23, 2014 4:39:39 pm Poul-Henning Kamp wrote:
> In message <201405231605.26312@freebsd.org>, John Baldwin writes:
>
> >In essence, top will consider any thread that has run on a CPU
> >since the last update as non-idle.
>
> Sounds a lot more usable than the current heuristic.
>
On 2014-05-23 16:05, John Baldwin wrote:
> Right now, when top is set to not display idle processes or threads, it only
> displays processes or threads that are currently in a runnable state or have
> a
> non-zero %cpu. However, our %cpu is quite imprecise. I have patch to change
> top to ins
In message <201405231605.26312@freebsd.org>, John Baldwin writes:
>In essence, top will consider any thread that has run on a CPU
>since the last update as non-idle.
Sounds a lot more usable than the current heuristic.
Wouldn't ki_rusage.ru_n[i]vcsw be more correct than ki_runtime ?
--
Po
On 22 May 2014 11:32, Rafael Espíndola wrote:
>
> The ConsoleControl.h file is copied from
> EdkCompatibilityPkg/Foundation/Protocol/ConsoleControl in
> https://github.com/tianocore/edk2.
I'm not aware of the full ancestry of our EFI include files, but it
looks like the initial import made some a
On 05/23/2014 15:05, John Baldwin wrote:
> Right now, when top is set to not display idle processes or threads, it only
> displays processes or threads that are currently in a runnable state or have
> a
> non-zero %cpu. However, our %cpu is quite imprecise. I have patch to change
> top to ins
Right now, when top is set to not display idle processes or threads, it only
displays processes or threads that are currently in a runnable state or have a
non-zero %cpu. However, our %cpu is quite imprecise. I have patch to change
top to instead compare the thread or processes runtime (ki_run
On Wed, May 14, 2014 at 09:58:52AM -0400, Shawn Webb wrote:
> Hey All,
>
> [NOTE: crossposting between freebsd-current@, freebsd-security@, and
> freebsd-stable@. Please forgive me if crossposting is frowned upon.]
>
> Address Space Layout Randomization, or ASLR for short, is an exploit
> mitigat
On May 23, 2014, at 8:07 AM, John Baldwin wrote:
> On Monday, May 19, 2014 4:12:50 pm Hans Petter Selasky wrote:
>> On 05/18/14 23:03, Hans Petter Selasky wrote:
>>> Hi,
>>>
>>> First call:
>>>
>>> resource_list_add:
>>
>> Hi,
>>
>> It appears that the /dev/pccard.X is opened and reading som
On May 13, 2014, at 5:04 PM, Don Lewis wrote:
> On 13 May, To: po...@freebsd.org wrote:
>> Please excuse the crosspost. I'm not sure if this is a ports problem or
>> a CURRENT problem.
>>
>> I just updated my 11.0-CURRENT machine to r265940 and can no longer
>> build ports/INDEX-11. My ports
On Monday, May 19, 2014 4:12:50 pm Hans Petter Selasky wrote:
> On 05/18/14 23:03, Hans Petter Selasky wrote:
> > Hi,
> >
> > First call:
> >
> > resource_list_add:
>
> Hi,
>
> It appears that the /dev/pccard.X is opened and reading some CIS data
> from the device before any driver has been atta
On Wednesday, May 21, 2014 3:43:49 pm Jan Henrik Sylvester wrote:
> On 05/21/2014 21:22, Hans Petter Selasky wrote:
> > On 05/21/14 21:16, Jan Henrik Sylvester wrote:
> >> Unfortunately, my USB mouse does not work anymore: After the first
> >> resume, it took a few seconds until it worked again (th
On 21.05.2014 21:43, Jan Henrik Sylvester wrote:
> On 05/21/2014 21:22, Hans Petter Selasky wrote:
>> On 05/21/14 21:16, Jan Henrik Sylvester wrote:
>>> Unfortunately, my USB mouse does not work anymore: After the first
>>> resume, it took a few seconds until it worked again (the build in
>>> touch
18 matches
Mail list logo
