On 22 Jan, Mike Tancsa wrote:
> On 1/22/2018 1:41 PM, Peter Moody wrote:
>> fwiw, I upgraded to 11-STABLE (11.1-STABLE #6 r328223), applied the
>> hw.lower_amd64_sharedpage setting to my loader.conf and got a crash
>> last night following the familiar high load -> idle. this was with SMT
>> re-enab
On 22 Jan, Mike Tancsa wrote:
> On 1/21/2018 3:24 PM, Don Lewis wrote:
>>>
>>> I have supplied a customer with a Ryzen5 and a 350MB motherboard.
>>> But he runs Windows 10, but I haven't heard him complain about anything
>>> like this.
>>> But I'll ask him specific.
>>
>> Only the BSDs were affec
On 1/21/2018 3:24 PM, Don Lewis wrote:
>>
>> I have supplied a customer with a Ryzen5 and a 350MB motherboard.
>> But he runs Windows 10, but I haven't heard him complain about anything
>> like this.
>> But I'll ask him specific.
>
> Only the BSDs were affected by the shared page issue. I think
On Mon, Jan 22, 2018 at 12:05 PM, FF wrote:
> oh nice! so it "just works" -- is there any way to verify it?
>
Not easily. You could try putting a load on those disks, then use "gstat
-a" to watch the queue depth (the "L(q)" column). If it's >1, that means
that geom is trying to use queued comm
oh nice! so it "just works" -- is there any way to verify it?
Is there any reason to use the highpoint driver when the native FreeBSD one
seems to work?
thanks!!
On Mon, Jan 22, 2018 at 1:26 PM, Alan Somers wrote:
> On Mon, Jan 22, 2018 at 11:08 AM, FF wrote:
>
>> I have a machine with the Hi
On 1/22/2018 1:41 PM, Peter Moody wrote:
> fwiw, I upgraded to 11-STABLE (11.1-STABLE #6 r328223), applied the
> hw.lower_amd64_sharedpage setting to my loader.conf and got a crash
> last night following the familiar high load -> idle. this was with SMT
> re-enabled. no crashdump, so it was the har
fwiw, I upgraded to 11-STABLE (11.1-STABLE #6 r328223), applied the
hw.lower_amd64_sharedpage setting to my loader.conf and got a crash
last night following the familiar high load -> idle. this was with SMT
re-enabled. no crashdump, so it was the hard crash that I've been
getting.
all of the build
On 1/22/2018 1:25 PM, Don Lewis wrote:
> On 22 Jan, Pete French wrote:
>>
>>
>> On 21/01/2018 19:05, Peter Moody wrote:
>>> hm, so i've got nearly 3 days of uptime with smt disabled.
>>> unfortunately this means that my otherwise '12' cores is actually only
>>> '6'. I'm also getting occasional segf
On Mon, Jan 22, 2018 at 11:08 AM, FF wrote:
> I have a machine with the Highpoint card and motherboard based SATA drives.
> The drives from the MB support AHCI and appear as ada0-8. The drives on the
> highpoint card whether using native FreeBSD support or the Highpoint
> provided driver show up
On 22 Jan, Pete French wrote:
>
>
> On 21/01/2018 19:05, Peter Moody wrote:
>> hm, so i've got nearly 3 days of uptime with smt disabled.
>> unfortunately this means that my otherwise '12' cores is actually only
>> '6'. I'm also getting occasional segfaults compiling go programs.
>
> Isn't go kn
I have a machine with the Highpoint card and motherboard based SATA drives.
The drives from the MB support AHCI and appear as ada0-8. The drives on the
highpoint card whether using native FreeBSD support or the Highpoint
provided driver show up as da9-39.
It is my understanding that AHCI is needed
Since upgrading my jail server to 11.1-RELEASE, the clock occasionally
jumps backwards by 5-35 minutes for no apparent reason. Has anybody seen
something like this?
Details
=
* Happens about once a day on my jail server, and has happened at least
once on a separate bhyve server.
* The jumps
On 22/01/2018 09:17, Scott Bennett wrote:
> Anyway, I'm stuck. Can someone please tell me what is going wrong and
> how to fix it? I'd really like to be able to update my system, not only to
> keep it reasonably current, but also to be able to customize a kernel. Thanks
> in advance for any
On 21/01/2018 19:05, Peter Moody wrote:
hm, so i've got nearly 3 days of uptime with smt disabled.
unfortunately this means that my otherwise '12' cores is actually only
'6'. I'm also getting occasional segfaults compiling go programs.
Isn't go known to have issues on BSD anyway though ? I ha
I tried asking for help on this several days ago on freebsd-questions@,
but got no responses. I'm trying freebsd-stable@ next because it involves
trying to build world on a 11.1-STABLE system from a freshly checked out,
unaltered source tree at r328251. The system currently installed is from
15 matches
Mail list logo