Received: from mx1.tetrasec.net (mx1.tetrasec.net [66.245.177.37]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id BEB4D780DE9 for <~alpine/devel@lists.alpinelinux.org>; Sat, 11 Jun 2022 21:23:46 +0000 (UTC) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 4282928A77C; Sat, 11 Jun 2022 21:23:45 +0000 (UTC) Received: from [10.97.7.178] (071-087-157-033.res.spectrum.com [71.87.157.33]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: nangel@tetrasec.net) by mx1.tetrasec.net (Postfix) with ESMTPSA id ECF5C28A77B; Sat, 11 Jun 2022 21:23:44 +0000 (UTC) Message-ID: Subject: Re: Kernel Panic on VIA Nano (x86_64) for 3.15 and above From: Nathan Angelacos To: Timo Teras Cc: ~alpine/devel <~alpine/devel@lists.alpinelinux.org> Date: Sat, 11 Jun 2022 17:23:43 -0400 In-Reply-To: <20220609214812.528b364f@vostro> References: <20220609214812.528b364f@vostro> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.2 MIME-Version: 1.0 On Thu, 2022-06-09 at 21:48 +0300, Timo Teras wrote: > Hi >=20 > Sounds like: > https://bugzilla.kernel.org/show_bug.cgi?id=3D212389 >=20 > Seems there's a patch, but it's not merged :/ Should probably ping on > kernel folks on this. Possible cherry-pick the patch if needed? > Nicely > there is a boot time cmdline workaround: > =C2=A0"initcall_blacklist=3Dinit_hw_perf_events" >=20 > Per https://gitlab.alpinelinux.org/alpine/tsc/-/issues/20=C2=A0i586 shoul= d > be the baseline for most things. So I'd assume VIA Nano should work > as > it's full i586 (instead of those cheap something in between i486 and > i586 things). >=20 > Timo >=20 Thanks Timo, That worked. (Although I can't believe you top-posted! :D)