Date: Sat, 30 Mar 2019 19:49:06 +0200 From: Darius Mihai <dariusmihaim@gmail.com> To: Rozhuk Ivan <rozhuk.im@gmail.com> Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Boot hang on ryzen based notebook Message-ID: <CAPj=67uK5hi21FHt=Yas0QofW0CbLBotYus=xQ6t0YGNWnmKrA@mail.gmail.com> In-Reply-To: <20190330204138.18fe8443@rimwks> References: <20190330164628.138a2bad@rimwks> <CAPj=67tECgp6bgB4U5xqa0Nnngz6tZjEH4pw4PPcFay7DBJopg@mail.gmail.com> <20190330204138.18fe8443@rimwks>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 30, 2019 at 7:41 PM Rozhuk Ivan <rozhuk.im@gmail.com> wrote: > > On Sat, 30 Mar 2019 16:37:06 +0200 > Darius Mihai <dariusmihaim@gmail.com> wrote: > > > > I haven't actually tried with FreeBSD, but Linux also seems to have a > > similar problem that can be fixed by disabling ACPI. > > See 11.13.2.3 in > > https://www.freebsd.org/doc/handbook/acpi-overview.html and tell us > > how it works. > > > > Panic with hint.apic.0.disabled="1": > https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203260&action=edit > > I try also hw.mca.enabled=0, but it panic on cpu_initclocks_bsp(). - "No usable event timer found!" You wrote "apic.0.disabled", not "acpi.0.disabled". Are you sure you wrote the correct command? You do not want to disable the APIC (interrupt controller), but the ACPI (control and power interface). On a side note, you wrote "current@freebsd.org", so I've added "freebsd-current@freebsd.org" (I hope that's what you originally meant). Darius
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPj=67uK5hi21FHt=Yas0QofW0CbLBotYus=xQ6t0YGNWnmKrA>