Date: Mon, 17 Jan 2022 02:01:57 +0100 From: Willem Jan Withagen <wjw@digiware.nl> To: Eugene Grosbein <eugen@grosbein.net> Cc: "stable@freebsd.org" <stable@freebsd.org> Subject: Re: Trying to boot a supermicro H8DMT board Message-ID: <86766549-be58-1125-867e-ae4c415e1bb4@digiware.nl> In-Reply-To: <2f49fd20-cb5a-5ccc-7f9b-0229bc8e14b1@grosbein.net> References: <8ac447b6-eaaf-0a8f-da69-27db15dd6f55@digiware.nl> <YeFUErC27C6ud5lf@in-addr.com> <e1972327-dcf8-3485-382b-39b9021946a6@digiware.nl> <YeFd9mdywqEuIJ0H@in-addr.com> <2ec39eef-d2e2-c55e-b032-43de86e71a57@digiware.nl> <3d87a0b3-7bed-453b-df23-4a258ea46fbb@grosbein.net> <d8e6c746-3ec1-9c21-d5e7-44dc9600bb0b@digiware.nl> <802cf542-979d-b8e1-3f71-616b026eb852@grosbein.net> <48f57581-1f39-9f57-0e44-19c2c2bb3aeb@digiware.nl> <a0315a54-aefa-a3a3-2ac3-94d6e9410961@grosbein.net> <eac3dcef-9183-8fa5-b0de-b70650235960@digiware.nl> <78a47e83-a339-0c79-0ee0-9e55be80c78b@grosbein.net> <d0dbce19-f5e5-3ff0-99d6-55a9c94a4b48@digiware.nl> <2f49fd20-cb5a-5ccc-7f9b-0229bc8e14b1@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15-1-2022 15:28, Eugene Grosbein wrote: > 15.01.2022 21:06, Willem Jan Withagen wrote: >> On 14-1-2022 17:41, Eugene Grosbein wrote: >>> 14.01.2022 23:34, Willem Jan Withagen wrote >>> >>>> That is it..... it is "dead" after that >>>> Does 14-CURRENT have KDB stuff preloaded, I could give it a shot. >>> I'm not sure, you'll have to try it yourself. >>> >>>> Otherwise I'd have to build 11.4 and go into KDB from there. >>>> >>>> What are the first things you need to know? >>> https://docs.freebsd.org/en/books/developers-handbook/book/ >>> >>> Look at the section "10.6. Debugging Deadlocks" as the problem looks like some deadlock (no panic, no progress). >>> >> I have tried all incarnations on that page. >> Even found https://gist.github.com/bijanebrahimi/f2eb0c620d81aa6234e121a0ddd88cc2 >> which I think has the info more organized. >> >> Can it be that the deadlock is too early for the DDB break to be triggered? > Maybe, can't tell for sure. I'm afraid you'll need to dig it more: > read the code and add more "prints" to the kernel. Got this a bit further by adding this to the config: options ACPI_DEBUG options VERBOSE_SYSINIT=1 But now it tells me: Table 'FACP' at 0xdffc0200 Table 'APIC' at 0xdffc0390 Table 'MCFG' at 0xdffc0460 Table 'OEMB' at 0xdffce040 Table 'SRAT' at 0xdffc50f0 ACPI: No SLIT table found done. subsystem 1000000 vm_mem_init(0)... So I guess that the ACPI stuff is done, and we're going to look at init-ing the subsystems. But how do I translate the number to a name? I guess it is the virtual memory init, since there is only on place that calls vm_mem_init. And that is from the sysinit chain. But I would expect things to be really bad if the system hangs in the VM initialisation? --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86766549-be58-1125-867e-ae4c415e1bb4>