On 2020-Feb-12 15:23:51 -0500, mike tancsa wrote:
>Not sure about the older Athlon CPUs, but the 2 generations of Ryzen's I
>have seem correct as well as an APU
>
>CPU: AMD GX-412TC SOC (998.17-MHz K8-class CPU)
OTOH, I'm not confident about temperatures on my APU.
Steve Kargl wrote:
Anyone else see
===> usr.bin/clang/lldb (all)
c++ -target x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -O2 -pipe -I/usr/src/contrib/llvm-project/lldb/include
-I/usr/obj/usr/src/amd64.amd64/usr.bin/clang/lldb
On Thu, 13 Feb 2020 07:00:36 +0100 Andrea Venturoli m...@netfence.it said
On 2020-02-12 23:17, Chris wrote:
> # dmidecode -t4 | grep AMD
> Manufacturer: AMD
> Version: AMD Athlon(tm) II X4 630 Processor
> # sysctl -a | grep tempe
> dev.cpu.3.temperature: 33.5C
> dev.cpu.2.temperature: 33.5C
> d
On 2020-02-12 23:17, Chris wrote:
# dmidecode -t4 | grep AMD
Manufacturer: AMD
Version: AMD Athlon(tm) II X4 630 Processor
# sysctl -a | grep tempe
dev.cpu.3.temperature: 33.5C
dev.cpu.2.temperature: 33.5C
dev.cpu.1.temperature: 33.5C
dev.cpu.0.temperature: 33.5C
Also works here:
> cat /var/r
Anyone else see
===> usr.bin/clang/lldb (all)
c++ -target x86_64-unknown-freebsd13.0
--sysroot=/usr/obj/usr/src/amd64.amd64/tmp
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -O2 -pipe
-I/usr/src/contrib/llvm-project/lldb/include
-I/usr/obj/usr/src/amd64.amd64/usr.bin/clang/lldb -march=bdver2
-I/
On Wed, 12 Feb 2020 15:23:51 -0500 mike tancsa m...@sentex.net said
On 2/12/2020 1:39 PM, Chris wrote:
> Hard as I try I can not get anything close to the actual temperature
> of the CPUs or cores while running on FreeBSD.
> Family: Athlon X4
> Manufacturer: AuthenticAMD
>
Not sure about
On 2020-02-12 15:23, mike tancsa wrote:
sysctl -a dev.cpu.0.temperature
Those sort of things seem to just "not work"(tm) on older type of
processors :
vesta#
vesta#
vesta# uname -apKU
FreeBSD vesta 12.1-RELEASE-p2 FreeBSD 12.1-RELEASE-p2 GENERIC amd64
amd64 1201000 1201000
vesta# sysctl
On 2/12/2020 1:39 PM, Chris wrote:
> Hard as I try I can not get anything close to the actual temperature
> of the CPUs or cores while running on FreeBSD.
> Family: Athlon X4
> Manufacturer: AuthenticAMD
>
Not sure about the older Athlon CPUs, but the 2 generations of Ryzen's I
have seem co
On 2020-02-12 18:22, Gleb Smirnoff wrote:
Hans already checked in his patch. Great!
You're welcome. Glad it worked.
--HPS
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send a
Hard as I try I can not get anything close to the actual temperature
of the CPUs or cores while running on FreeBSD.
I assembled the following box as an intended builder for FreeBSD
Install images, upgrade images, and ports development, and package
builder / installer.
But to no avail. I'm unwillin
On Wed, Feb 12, 2020 at 09:18:32AM -0800, Gleb Smirnoff wrote:
T> On Wed, Feb 12, 2020 at 07:41:54PM +0300, y...@mm.st wrote:
T> y> Gleb Smirnoff wrote:
T> y> > On Wed, Feb 12, 2020 at 09:49:12AM +0300, y...@mm.st wrote:
T> y> > y> Getting the following panic after updating to r357793 (expect typos
On Wed, Feb 12, 2020 at 07:41:54PM +0300, y...@mm.st wrote:
y> Gleb Smirnoff wrote:
y> > On Wed, Feb 12, 2020 at 09:49:12AM +0300, y...@mm.st wrote:
y> > y> Getting the following panic after updating to r357793 (expect typos,
hand
y> > y> copied):
y> > y>
y> > y> panic: Assertion in_epoch(net_epoc
Gleb Smirnoff wrote:
On Wed, Feb 12, 2020 at 09:49:12AM +0300, y...@mm.st wrote:
y> Getting the following panic after updating to r357793 (expect typos, hand
y> copied):
y>
y> panic: Assertion in_epoch(net_epoch_preempt) failed at
y> /usr/src/sys/net/iflib.c:2762
y>
y> db_trace_self_wrapper()
y>
On Wed, Feb 12, 2020 at 09:49:12AM +0300, y...@mm.st wrote:
y> Getting the following panic after updating to r357793 (expect typos, hand
y> copied):
y>
y> panic: Assertion in_epoch(net_epoch_preempt) failed at
y> /usr/src/sys/net/iflib.c:2762
y>
y> db_trace_self_wrapper()
y> vpanic()
y> panic()
y
Hello Conrad,
thanks for the information and for contributing the driver in the first
place!
I'll stick with the hint for now.
Best regards
Andreas
On Tue, Feb 11, 2020 at 9:05 PM Conrad Meyer wrote:
> Hi Andreas,
>
> No, nothing new on this front. I don't have any of this hardware nor
> do
ср, 12 февр. 2020 г., 06:23 Thomas Mueller :
> from Andrey Fesenko:
>
> > bsdinstall script, work in 2019
>
> PARTITIONS="$DISKSLICE GPT { 512K freebsd-boot, 1M efi, auto freebsd-ufs
> / }
> #!/bin/sh -x
> # Make diskname independante
> gpart modify -l freebsd-boot -i 1 ada0
> gpart modify -l
On 2020-02-12 10:10, y...@mm.st wrote:
Hans Petter Selasky wrote:
Hi,
Does the attached patch fix the issue?
It seems to help, yes, at least no panic right after the boot.
Let us know if this happens again. There is currently some ongoing work
in this area.
https://svnweb.freebsd.org/cha
Hans Petter Selasky wrote:
Hi,
Does the attached patch fix the issue?
It seems to help, yes, at least no panic right after the boot.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscrib
Hi,
Does the attached patch fix the issue?
--HPS
Index: sys/net/iflib.c
===
--- sys/net/iflib.c (revision 357799)
+++ sys/net/iflib.c (working copy)
@@ -6060,6 +6060,7 @@
gtask = &ctx->ifc_txqs[qid].ift_task;
tqg = qgroup_if_i
19 matches
Mail list logo
