https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513
--- Comment #24 from stockhau...@collogia.de ---
One step further:
The wrong ACPI definitions are indeed the culprit of the wrong C2 state
registration. I implemented a lousy patch in acpi.c:
/*
* Pre-allocate/manage all memory and IO res
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513
--- Comment #23 from stockhau...@collogia.de ---
ok. ignore comment #22 i try to explain it once again. The problem seems to be
the other way round.
CPU wants to register port 0x414 for C state handling. This should be covered
by BIOS ACPI
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513
--- Comment #22 from stockhau...@collogia.de ---
After a lot of investigation it seems to boil down to some kind of timing
problem.
acpi_resource.c:acpi_res_set_ioport() is called for the ACPI defined
ressources. In our case there are sever
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513
--- Comment #21 from stockhau...@collogia.de ---
And one OpenBSD evidence about an AMD mobile CPU that has exactly our setup:
http://openbsd-archive.7691.n7.nabble.com/Disabled-USB-port-td328343.html
acpicpu0 at acpi0: C2(0@400 io@0x414), C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513
--- Comment #20 from stockhau...@collogia.de ---
Memo for myself: Seems as if port 0x414 is only available for core0 and not the
other ones. Maybe that is the source of the registration error.
At least there are other devinfo outputs that s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513
--- Comment #19 from stockhau...@collogia.de ---
(In reply to stockhausen from comment #18)
Attached.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513
--- Comment #18 from stockhau...@collogia.de ---
Created attachment 203132
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203132&action=edit
devinfo -rv
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513
--- Comment #17 from Andriy Gapon ---
Could you please also add devinfo -rv output?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513
--- Comment #16 from stockhau...@collogia.de ---
Created attachment 203120
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203120&action=edit
pciconf Output
--
You are receiving this mail because:
You are the assignee for the bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513
--- Comment #15 from stockhau...@collogia.de ---
(In reply to Andriy Gapon from comment #12)
Attached as requested
--
You are receiving this mail because:
You are the assignee for the bug.
___
f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513
--- Comment #14 from stockhau...@collogia.de ---
Created attachment 203117
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203117&action=edit
acpudump -dt of T620
--
You are receiving this mail because:
You are the assignee for t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513
--- Comment #13 from stockhau...@collogia.de ---
Created attachment 203116
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203116&action=edit
dmesg of T620 FreeBSD 12 boot
--
You are receiving this mail because:
You are the assig
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513
--- Comment #12 from Andriy Gapon ---
Has anyone attached an acpidump from an affected system yet?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@free
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236513
stockhau...@collogia.de changed:
What|Removed |Added
Summary|Different power states |AMD Jaguar: Only CPU core
14 matches
Mail list logo
