On Fri, 19 Oct 2018, Dr.Boutari wrote:
> 1 months ago I installed Openbsd 6.3 amd64.
> The cd and hdd boot will do a shutdown panic without providing 
> informative messages. Leading me to randomly try to disable acpi on 
> kernel boot and continue setup which worked. I soon figured out 
> afterwards I was only running one core of my multicore CPU and I thought 
> maybe I did press something wrong during install.

On many modern machines, ACPI _is_ how the OS can find the other CPUs.


> Firmware updated post install then I moved to stable then current brach 
> for another reason(another kernel panic due to radeondrm which was fixed 
> on current branch).
> 
> I knew 6.4 stable was coming so I waited to reinstall.

If no one is supplying the information to fix the issues with this 
hardware, it will only get fixed by luck.  You were not lucky.

> Yesterday tried booting 6.4 amd64 cd and it still shutdown crashes. 
> Disabled acpi like before and continued setup leading me to the sets. Im 
> not offered bsd.mp set so my cpu isnt well recognised.

Totally expected: see above.

> As a final trial I tried the 6.4 i386 cd boot. It crashes aswell but 
> doesnt shutdown and Im provided with an error message this time so Im 
> providing that as an attachment.Bypassing the crash with disable acpi 
> also leads me to the base sets install without offering the bsd.mp 
> kernel.

Totally expected: see above.

> Thanks for any provided help and if I could do anything to make this 
> issue more clear im ready to do that,so just give me suggestions.

At a _minimum_, you should generate a full bug report by running sendbug 
*as root*, verifying it includes
 - the full dmesg (albeit with acpi disabled)
 - pcidump(8) output
 - acpidump(8) output

If it includes all of those, then email it to <[email protected]>

If it doesn't include those, then don't bother emailing it in, as without 
those we can only guess what the problem is...and no one is going to waste 
their time trying to guess what the problem is.


Philip Guenther

Reply via email to