From owner-freebsd-amd64@freebsd.org Sat Apr 6 17:14:27 2019 Return-Path: Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7335D1565130 for ; Sat, 6 Apr 2019 17:14:27 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it1-f174.google.com (mail-it1-f174.google.com [209.85.166.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C2E389807 for ; Sat, 6 Apr 2019 17:14:26 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it1-f174.google.com with SMTP id y10so14689093itc.1 for ; Sat, 06 Apr 2019 10:14:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=+0RSrHU1XZ5vHtNyC9j4LtDGRx/KQFuG03E+nAcoKp0=; b=av3JTPOuoooUNg20vyvZdfm2bXDw0ziHzvcXj2q+WOuaKzielqLmVZ4V5XtPOQR0rt 1/3+3Hr/mVwtTRpekWxVu83Mn++1LnbJZBBhKIInEIRo68Rc4Z4Rrmm1Tnm2ERVXX18b 0KujcPENaLRkU3+OKVF4emxf/1hp3dsfANwwvgM9Z5Obxpg6XyzK0KYtr/Nzyb4gvPgb M6CF7roaNUSiglhAHWA0dFiRHWn+eGuXE5PYHoWUKN7tmn8tlLzysTcqMX43hvX3XYvC WhuBKb0Rr+OWcgaCZ3q10tATuuItkXze9zf4+QVDZdicaMxXy3YKKYq/Bv7Rw2TV5moa EA5A== X-Gm-Message-State: APjAAAUte0HugTqG2B2VMMJBYbaZlLRGxvoo5H0zAQrLlxdCYn2iGqw5 IRZBDVTIGDe3TcuS0QOAmyDpdSUs X-Google-Smtp-Source: APXvYqxm9U8OxnPlCu/k1nqau4bzYkyWgEHUdX+ggq/JbrTVRojdhb4lAUVsakExvw13O6gSlm9T4g== X-Received: by 2002:a24:70d3:: with SMTP id f202mr10031376itc.54.1554570865213; Sat, 06 Apr 2019 10:14:25 -0700 (PDT) Received: from mail-it1-f180.google.com (mail-it1-f180.google.com. [209.85.166.180]) by smtp.gmail.com with ESMTPSA id c99sm2754415itd.4.2019.04.06.10.14.24 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 06 Apr 2019 10:14:24 -0700 (PDT) Received: by mail-it1-f180.google.com with SMTP id y10so14689056itc.1 for ; Sat, 06 Apr 2019 10:14:24 -0700 (PDT) X-Received: by 2002:a02:9f93:: with SMTP id a19mr14461114jam.123.1554570864759; Sat, 06 Apr 2019 10:14:24 -0700 (PDT) MIME-Version: 1.0 References: <403763BB-4DB9-488F-9480-C71871ED66B5@yahoo.com> <20190405114617.GC1923@kib.kiev.ua> <20190406165031.GK1923@kib.kiev.ua> In-Reply-To: <20190406165031.GK1923@kib.kiev.ua> Reply-To: cem@freebsd.org From: Conrad Meyer Date: Sat, 6 Apr 2019 10:14:13 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: head -r345758 Ryzen Threadripper 1950X vs. amdtemp.ko : dev.cpu.31 missing To: Konstantin Belousov Cc: Mark Millard , freebsd-amd64@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 0C2E389807 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.991,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Apr 2019 17:14:27 -0000 amdtemp attaching under hostb is normal. The only oddity here is the missing cpu31. My guess is BIOS bug? I have a 1950x and it reports all 32 cores correctly. Best, Conrad On Sat, Apr 6, 2019 at 9:51 AM Konstantin Belousov wrote: > > On Fri, Apr 05, 2019 at 11:47:58AM -0700, Mark Millard wrote: > > > > > > On 2019-Apr-5, at 04:46, Konstantin Belousov wrote: > > > > > On Thu, Apr 04, 2019 at 04:58:15PM -0700, Mark Millard via freebsd-amd64 wrote: > > >> On a: > > >> > > >> CPU: AMD Ryzen Threadripper 1950X 16-Core Processor (3393.70-MHz K8-class CPU) > > >> Origin="AuthenticAMD" Id=0x800f11 Family=0x17 Model=0x1 Stepping=1 > > >> Features=0x178bfbff > > >> Features2=0x7ed8320b > > >> AMD Features=0x2e500800 > > >> AMD Features2=0x35c233ff > > >> Structured Extended Features=0x209c01a9 > > >> XSAVE Features=0xf > > >> AMD Extended Feature Extensions ID EBX=0x1007 > > >> SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=32768 > > >> TSC: P-state invariant, performance statistics > > >> > > >> after "kldload amdtemp" the following is seen: > > >> > > >> # sysctl dev.cpu.31 > > >> sysctl: unknown oid 'dev.cpu.31' > > >> > > >> # sysctl dev.cpu.30 > > >> dev.cpu.30.temperature: 62.1C > > >> dev.cpu.30.cx_method: C1/hlt C2/io > > >> dev.cpu.30.cx_usage_counters: 0 0 > > >> dev.cpu.30.cx_usage: 0.00% 0.00% last 1000000us > > >> dev.cpu.30.cx_lowest: C1 > > >> dev.cpu.30.cx_supported: C1/1/0 C2/2/100 > > >> dev.cpu.30.%parent: acpi0 > > >> dev.cpu.30.%pnpinfo: _HID=none _UID=0 > > >> dev.cpu.30.%location: handle=\_PR_.C01F > > >> dev.cpu.30.%driver: cpu > > >> dev.cpu.30.%desc: ACPI CPU > > >> > > >> . . . > > > > > > In the output of devinfo(8), how many CPUs do you see ? Is there cpu31, > > > and does it have amdtemp child ? > > > > (I only used 'sysctl -a | grep "temp.*[0-9]C$"' as a short > > way to show one line per dev.cpu.N so show the others were > > all present.) > > > > cpu31 is missing in the devinfo output. The amdtempM's are under > > pcibX > pciY > hostbZ , not per cpuN . > > > > Shortended output but showing all the cpuN and amdtmpM > > and their "parents" and "childern": > > > > # devinfo > > nexus0 > > cryptosoft0 > > vtvga0 > > apic0 > > ram0 > > acpi0 > > cpu0 > > hwpstate0 > > cpufreq0 > > cpu1 > > cpu2 > > cpu3 > > cpu4 > > cpu5 > > cpu6 > > cpu7 > > cpu8 > > cpu9 > > cpu10 > > cpu11 > > cpu12 > > cpu13 > > cpu14 > > cpu15 > > cpu16 > > cpu17 > > cpu18 > > cpu19 > > cpu20 > > cpu21 > > cpu22 > > cpu23 > > cpu24 > > cpu25 > > cpu26 > > cpu27 > > cpu28 > > cpu29 > > cpu30 > > pcib0 > > pci0 > > hostb0 > > amdsmn0 > > amdtemp0 > > . . , > > pcib12 > > pci12 > > hostb23 > > amdsmn1 > > amdtemp1 > > . . . > > Ok, I see, it was unexpected to see amdtemp to attach under the host > bridge instead of cpu device. Please post complete output of devinfo -r > and pciconf -lvcb somewhere. > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org"