From nobody Wed Aug 03 16:28:21 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4LyckR22zpz4Y5Cy for ; Wed, 3 Aug 2022 16:29:03 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from fry.fubar.geek.nz (fry.fubar.geek.nz [139.59.165.16]) by mx1.freebsd.org (Postfix) with ESMTP id 4LyckP0XMmz3vv5 for ; Wed, 3 Aug 2022 16:29:00 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from smtpclient.apple (cpc91232-cmbg18-2-0-cust554.5-4.cable.virginm.net [82.2.126.43]) by fry.fubar.geek.nz (Postfix) with ESMTPSA id C3D784E706; Wed, 3 Aug 2022 16:28:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fubar.geek.nz; s=mail; t=1659544102; bh=PPNIWnZkk3ZDhcU8aZX9/LyLu49gNrIv4HOjz3EEO0k=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=Tk1IpzBdGsv5RpQQItJ/LHFWl+U9JG8fLD9cmy77+SqJftwlOcjiOFCqb1R58uWw8 EuvCbboBEKCmrdFqSsFiTRem+Qqqu9rQk4axMEU3yxagh4lcn+i7s95N3Xjkx2+z1I oz1wHRTV4x3TzO6DsItEL1866L4tKg7aQj0wQvfk0OVAg2ccNbnWEFO8btjP0C73/5 m7eC/hEV8uNbQslYGBF5nZSTVgJIv10nM6NVT6CLsr76d1Ww/LBp645hE+zbQnE/X/ RfE8bE/aP5pnI+kasq1VBgLn89Ku0cTAUf5arb/Fbj0w0qmoJbf0zP1j38zoky1J4z axEdWpGbXSiCffuzHbvNcLS0hf81Tls3Jw+3EcPQ1YxxqQCrS2SRp3PKaBxF5a2DhD plfhCq1rTLBuheduoLxTyLxvp4Q67C5etGDU2/FbSPxR4YwE6Rl4GXxN+obV08LDJk DpW2twod8PKCKjXsbYAtYwtRl/y5EU1CSLaqR1lZ+zMF3FEt2xvjqPBstr4ScDMMDy 1KLks6BIStkUPiCYrYD9uXnwpbHRuroubF9NvphcbWA+lrn3GV4UaarniMXzZ3aQ1x e9x/UWgd5ytdNlvt8/MErT4Q7nXgSBAeW6aEj5cfeXRvfkt335V15PrX0rvFBe5jM/ uv5SCfrh5xEQxTsIsicPQxBY= Content-Type: text/plain; charset=utf-8 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\)) Subject: Re: ARM64 system error From: Andrew Turner In-Reply-To: <82D60642-4087-4EED-B790-F8FE81A188C5@mit.edu> Date: Wed, 3 Aug 2022 17:28:21 +0100 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: References: <82D60642-4087-4EED-B790-F8FE81A188C5@mit.edu> To: John F Carr X-Mailer: Apple Mail (2.3696.100.31) X-Rspamd-Queue-Id: 4LyckP0XMmz3vv5 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=fubar.geek.nz header.s=mail header.b=Tk1IpzBd; dmarc=pass (policy=none) header.from=fubar.geek.nz; spf=softfail (mx1.freebsd.org: 139.59.165.16 is neither permitted nor denied by domain of andrew@fubar.geek.nz) smtp.mailfrom=andrew@fubar.geek.nz X-Spamd-Result: default: False [0.30 / 15.00]; VIOLATED_DIRECT_SPF(3.50)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW_WITH_FAILURES(-0.50)[]; MV_CASE(0.50)[]; R_DKIM_ALLOW(-0.20)[fubar.geek.nz:s=mail]; RCVD_NO_TLS_LAST(0.10)[]; MIME_GOOD(-0.10)[text/plain]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; ASN(0.00)[asn:14061, ipnet:139.59.160.0/20, country:US]; DMARC_POLICY_ALLOW(0.00)[fubar.geek.nz,none]; DKIM_TRACE(0.00)[fubar.geek.nz:+]; MID_RHS_MATCH_FROM(0.00)[]; FREEFALL_USER(0.00)[andrew]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; TO_DN_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-ThisMailContainsUnwantedMimeParts: N > On 31 Jul 2022, at 17:55, John F Carr wrote: >=20 > My OverDrive 1000 (Cortex A57) running CURRENT just crashed with the = unhelpful message "panic: Unhandled System Error". Is there any way to = get better information? The ESR value bf000000 translates to "system = error with implementation-defined code 0" so that's not much use. The = instruction associated with the interrupt can't fault ("subs w22, w22, = #0x1") so it must be an asynchronous error. On other systems I've seen = bits you can test or registers you can read to get details. By my reading of the Cortex-A57 documentation [1] I think the ESR value = shows the exception can be attributed to the current core, is = containable to a given code sequence, and is a decode error. It=E2=80=99s likely due to msk_phy_readreg accessing the phy, but it = doesn=E2=80=99t respond quickly enough. Does an older kernel boot? If so can you try bisecting to find which = commit caused the panic. Andrew [1] Bottom of = https://developer.arm.com/documentation/ddi0488/h/system-control/aarch64-r= egister-descriptions/exception-syndrome-register--el1-and-el3?lang=3Den >=20 > x0: 0 > x1: ffff0000b55bd000 (crypto_dev + b3f34ec0) > x2: 2880 > x3: 20 > x4: d3 > x5: 0 > x6: 100 > x7: ffff00011063daa0 > x8: ffff00000077218c (generic_bs_r_2 + 0) > x9: 2880 > x10: ffff0000001ff9f4 (msk_phy_readreg + 84) > x11: a0000045 > x12: 56000000 > x13: 5e4a6f28 > x14: ffff000000c4d038 (vnet_entry_ipport_stoprandom + 0) > x15: ffffa000016b3000 > x16: 40ef9400 > x17: a > x18: ffff0000b550e560 (crypto_dev + b3e86420) > x19: ffff0000b57dc000 (crypto_dev + b4153ec0) > x20: ffffa000029dc800 > x21: 2880 > x22: 3c4 > x23: 796d > x24: ffffa000017f4100 > x25: ffff000000ad3da0 (miibus_readreg_desc + 0) > x26: ffff000000bb6000 (vop_deallocate_desc + 28) > x27: ffff000000e36980 (cc_cpu + 80) > x28: ffff000000b1b828 (lock_class_mtx_sleep + 0) > x29: ffff0000b550e670 (crypto_dev + b3e86530) > sp: ffff0000b550e560 > lr: ffff0000001ff9f0 (msk_phy_readreg + 80) > elr: ffff00000077806c (handle_el1h_irq + 8) > spsr: a00002c5 > far: 0 > esr: bf000000 > panic: Unhandled System Error > cpuid =3D 2 > time =3D 1659270153 > KDB: stack backtrace: > db_trace_self() at db_trace_self > db_trace_self_wrapper() at db_trace_self_wrapper+0x30 > vpanic() at vpanic+0x13c > panic() at panic+0x44 > do_serror() at do_serror+0x40 > handle_serror() at handle_serror+0x38 > --- system error, esr 0xbf000000 > handle_el1h_irq() at handle_el1h_irq+0x8 > --- interrupt > msk_phy_readreg() at msk_phy_readreg+0x84 > e1000phy_status() at e1000phy_status+0x114 > e1000phy_service() at e1000phy_service+0x420 > mii_tick() at mii_tick+0x50 > msk_tick() at msk_tick+0x44 > softclock_call_cc() at softclock_call_cc+0x128 > softclock_thread() at softclock_thread+0xc4 > fork_exit() at fork_exit+0x74 > fork_trampoline() at fork_trampoline+0x14 > KDB: enter: panic > [ thread pid 2 tid 100026 ] > Stopped at kdb_enter+0x44: undefined f907c27f >=20