Bug 262690 - "driver bug: Unable to set devclass" for atrtc
Summary: "driver bug: Unable to set devclass" for atrtc
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 13.0-STABLE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-20 19:20 UTC by John F. Carr
Modified: 2023-10-19 22:11 UTC (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John F. Carr 2022-03-20 19:20:19 UTC 
At boot my kernel reports

driver bug: Unable to set devclass (class: atrtc devname: (unknown))

device_set_devclass is returning 17 (EEXIST).  According to my old system logs this started showing up in December 2020 when I upgraded from

FreeBSD 13.0-CURRENT #0 r366363: Fri Oct  2 13:36:14 EDT 2020

to

FreeBSD 13.0-CURRENT #0 r368445: Tue Dec  8 11:52:41 EST 2020

My hardware is an HPE ProLiant DL325 with a single AMD EPYC 7402P 24 core CPU.

Surrounding context is

intsmb0: <AMD FCH SMBus Controller> at device 20.0 numa-domain 0 on pci15
smbus0: <System Management Bus> numa-domain 0 on intsmb0
driver bug: Unable to set devclass (class: atrtc devname: (unknown))
acpi_wmi0: <ACPI-WMI mapping> on acpi0
acpi_wmi0: cannot find EC device
lo0: link state changed to UP
Comment 1 Bunny Evans 2023-06-05 06:59:28 UTC 
This is present on an ML30 gen10 too:

FreeBSD turbinia 13.2-RELEASE FreeBSD 13.2-RELEASE releng/13.2-n254617-525ecfdad597 GENERIC amd64


uhub_explore: illegal enable change, port 1
uhub_explore: illegal enable change, port 4
pchtherm0: <CannonLake-H Thermal Subsystem> mem 0x4000006000-0x4000006fff at device 18.0 numa-domain 0 on pci0
driver bug: Unable to set devclass (class: atrtc devname: (unknown))
acpi_wmi0: <ACPI-WMI mapping> on acpi0
acpi_wmi0: cannot find EC device
Comment 2 Michael Dexter 2023-10-19 22:11:54 UTC 
For what it's worth, I am seeing this same error message on an HPE ML110 Gen9 with FreeBSD 13.2-RELEASE-p4.

Interestingly, this is also seen in a bhyve VM.