On 13/12/2018 12:56, Sascha Klauder wrote:> So far, I tried (unsuccessfully) to disable obvious ACPI sub- > systems (cpu, mwait, quirks) and debug settings (acpi.cpu_unordered, > acpi.max_threads). Anyone got a hint where to look or debug this > further?Are you able to identify if you have a hardware or a software hang? E.g., are you able to enter ddb?> kernel boot messages (obtained from 10.4 amd64): > https://lair.griffinsplace.de/~sascha/phenom/dmesg-freeze-FreeBSD10.txt > > boot messages with the previous Athlon II cpu in this system: > https://lair.griffinsplace.de/~sascha/phenom/dmesg-FreeBSD-AthlonII.txt > > boot messages from DFly, OpenBSD and Linux: > https://lair.griffinsplace.de/~sascha/phenom/-- Andriy Gapon
On Fri, 2018-12-14 11:56 +0200, Andriy Gapon wrote:> On 13/12/2018 12:56, Sascha Klauder wrote: > > So far, I tried (unsuccessfully) to disable obvious ACPI sub- > > systems (cpu, mwait, quirks) and debug settings (acpi.cpu_unordered, > > acpi.max_threads). Anyone got a hint where to look or debug this > > further? > Are you able to identify if you have a hardware or a software hang? > E.g., are you able to enter ddb?Hardware; can't enter ddb and can't toggle caps lock. I could probably setup remote GDB (serial) but would need some pointer how to proceed from there. Cheers, -sascha