On 14/12/2018 21:37, Sascha Klauder wrote: > 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.
The only idea I have is to boot to ddb (boot_ddb="YES" or boot -d), set a breakpoint in a function from which the last printed line comes[*], continue until the breakpoint is hit and then step from there trying to narrow down a function (or even an instruction) where the hang happens. [*] - seems to be pcie_cfgregopen() -- Andriy Gapon _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
