NetBSD Problem Report #56505

From www@netbsd.org  Wed Nov 17 16:45:41 2021
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 833001A9239
	for <gnats-bugs@gnats.NetBSD.org>; Wed, 17 Nov 2021 16:45:41 +0000 (UTC)
Message-Id: <20211117164540.012AD1A923A@mollari.NetBSD.org>
Date: Wed, 17 Nov 2021 16:45:39 +0000 (UTC)
From: jspath55@gmail.com
Reply-To: jspath55@gmail.com
To: gnats-bugs@NetBSD.org
Subject: amdzentemp0: autoconfiguration error: unable to register with sysmon (error=22)
X-Send-Pr-Version: www-1.0

>Number:         56505
>Category:       port-amd64
>Synopsis:       amdzentemp0: autoconfiguration error: unable to register with sysmon (error=22)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    msaitoh
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Nov 17 16:50:00 +0000 2021
>Closed-Date:    Fri May 10 03:41:52 +0000 2024
>Last-Modified:  Fri May 10 03:41:52 +0000 2024
>Originator:     Jim Spath
>Release:        NetBSD 9.2
>Organization:
n/a
>Environment:
NetBSD machine.domain 9.2 NetBSD 9.2 (GENERIC) #0: Wed May 12 13:15:55 UTC 2021  mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64
>Description:
I have a new ASUS motherboard with a AMD Ryzen 5 5600X 6-Core Processor.
Was looking for environmental sensors such as CPU temperature, and see these messages in dmesg:

[     1.002665] amdsmn0 at pci0 dev 0 function 0: AMD System Management Network
[     1.002665] amdzentemp0 at amdsmn0: AMD CPU Temperature Sensors (Family19h)
[     1.002665] amdzentemp0: autoconfiguration error: unable to register with sysmon (error=22)

The envstat command returns no drivers:

$ envstat
envstat: no drivers registered

>How-To-Repeat:
Happens on boot.
>Fix:
Unknown.

>Release-Note:

>Audit-Trail:
From: mlelstv@serpens.de (Michael van Elst)
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: port-amd64/56505: amdzentemp0: autoconfiguration error: unable to register with sysmon (error=22)
Date: Wed, 17 Nov 2021 17:09:40 -0000 (UTC)

 jspath55@gmail.com writes:

 >I have a new ASUS motherboard with a AMD Ryzen 5 5600X 6-Core Processor.
 >Was looking for environmental sensors such as CPU temperature, and see these messages in dmesg:

 >[     1.002665] amdsmn0 at pci0 dev 0 function 0: AMD System Management Network
 >[     1.002665] amdzentemp0 at amdsmn0: AMD CPU Temperature Sensors (Family19h)
 >[     1.002665] amdzentemp0: autoconfiguration error: unable to register with sysmon (error=22)


 Ryzen 5 5600X is Family 0x19 (Zen3). The amdzentemp driver in netbsd-9 doesn't know about that
 and tries to attach a device without sensors. That yields the error=22 (EINVAL).

From: Jim Spath <jspath55@gmail.com>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: port-amd64/56505: amdzentemp0: autoconfiguration error: unable to
 register with sysmon (error=22)
Date: Thu, 9 May 2024 08:51:47 -0400

 This problem was reported for NetBSD 9.2; since then I've upgraded the
 machine to 10.0.
 As the symptoms have been fixed, OK to close this ticket.

 >  Ryzen 5 5600X is Family 0x19 (Zen3). The amdzentemp driver in netbsd-9 doesn't know about that
 >  and tries to attach a device without sensors. That yields the error=22 (EINVAL).

 $ dmesg | grep amdzen
 [     1.028186] amdzentemp0 at amdsmn0: AMD CPU Temperature Sensors (Family19h)

 $ envstat
                            Current  CritMax  WarnMax  WarnMin  CritMin  Unit
 [amdzentemp0]
        cpu0 temperature:    39.875                                      degC
   cpu0 ccd0 temperature:    40.500                                      degC

Responsible-Changed-From-To: port-amd64-maintainer->msaitoh
Responsible-Changed-By: riastradh@NetBSD.org
Responsible-Changed-When: Thu, 09 May 2024 16:17:09 +0000
Responsible-Changed-Why:
msaitoh: Can you assess whether the fixes for this are reasonable to
pull up to netbsd-9, and either pull them up or close the PR if it's
too much work?

(Tagging you because you made the last few changes to amdzentemp.c.)


State-Changed-From-To: open->needs-pullups
State-Changed-By: riastradh@NetBSD.org
State-Changed-When: Thu, 09 May 2024 16:17:09 +0000
State-Changed-Why:
might need pullups


State-Changed-From-To: needs-pullups->closed
State-Changed-By: msaitoh@NetBSD.org
State-Changed-When: Fri, 10 May 2024 03:41:52 +0000
State-Changed-Why:
All changes to amdsmn(4) and amdzentemp(4) in -current were pulled up to netbsd-{9,10}.
Thanks.


>Unformatted:

Home	PR Database Search