Date: Mon, 17 Jan 2022 20:46:24 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Willem Jan Withagen <wjw@digiware.nl>, stable@freebsd.org Subject: Re: Trying to boot a supermicro H8DMT board Message-ID: <9d73e9ba-af23-ea90-e5fa-cf3a04a8513b@grosbein.net> In-Reply-To: <c6588210-ac68-f081-f0a4-85669aa84eb3@digiware.nl> 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> <86766549-be58-1125-867e-ae4c415e1bb4@digiware.nl> <7903a41f-94ba-2caf-9270-a1bd9582c600@grosbein.net> <229c3042-3297-7903-9778-9b55d5c3f998@digiware.nl> <71d1e25c-f1f6-2371-486e-2382d67a3fc5@grosbein.net> <c6588210-ac68-f081-f0a4-85669aa84eb3@digiware.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
17.01.2022 20:24, Willem Jan Withagen wrote: >> Well, perform independent hardware (memory) testing with something like memtest86+ >> and if it is all right, you show ask someone more knowledgeable. Maybe CC: arch@freebsd.org > > Perhaps should have done that when I started, but supplier assured me that > the they just retired the boards with out any issues. > Memtest86 found the faulty DIMM in 30 secs... > > Not sure if we could/want educate vm_mem_init() to actually detect this. > It is still in the part where everthing is still running on the first CPU. > Making things a bit easier to understand what is going on. > > Lets see if the box will run on 3 DIMMs for the rime being. > Then figure out with DMIdecode what we need expand again. Is it ECC memory or non-ECC? The kernel already have full memory testing performed at boot time unless disabled with another loader knob: hw.memtest.tests=0 Try booting it with memory testing disabled and without hw.physmem limitation. Maybe it will boot. With ECC, it could be hardware interrupt while kernel runs that test and wrong in-kernel processing of the interrupt.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9d73e9ba-af23-ea90-e5fa-cf3a04a8513b>