From nobody Mon Sep 4 15:32:41 2023 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 4RfXhD158Cz4sHdg; Mon, 4 Sep 2023 15:32:44 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RfXhD0f2dz3TKv; Mon, 4 Sep 2023 15:32:44 +0000 (UTC) (envelope-from kevans@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1693841564; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WnMfo/YdMJSmNHHjRE4rIpFGDmSIEwOltYFTzlE5W2s=; b=cSaK2fjXWznCF1/T/GkOq4ov3Mt3eFaNb3BaW4DtEXZWMqLuh6gXsXn0jv9vzaYW1xklXs uELpBL9EFDOvbhnU3zxcgi+gVxOR1cBz3f83lcEpOGOxzACoeO286DK6FFn+3Kt34G3b5G Ra1fqTe3Jp8n4v9nECxGxjUUniFlWso7UH40bNdGYHhfPFIPbq+jX7gyp8+w6xQD1xWNJk BWpoyEUOEI/aoQLQJgXhi8zcOPmVydtbdVX6IFtCIa8f/UhfCQ1kfpirjuT0GvJ9Bd2NJg CDvwDKAGLLqFO1KfiS2MWHW2VqWvZF932rTLxrymZngFVaGxqfTA5X5RWIHU1A== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1693841564; a=rsa-sha256; cv=none; b=fdh5jazgox3MohRxSFmIQeToM+eNo4vcFRPgkM61TAHxYTYZu2tIhoHk8DNhI+7W4u0TOw QWIaFmizmWNMoltyZ7f2eP4nnI0VENdgG0uqbPlzkWph1HIRoyMgi7PvqTNAdruraGaUdK F/+cT174tSwCJAcWuzPOd++8QPv/02XjVNAjIbklRHOk1M3cjjpjAk9pN46/9BW2+RG1gZ 0E6XCwyVMfepEyD08+uNsYzU17TSpEdq8sH7uyhZ7mv61ZEkguUW6aHsVVWGs/i1cR/1v0 QRR5oyM90dQf9D19npCWHRIx2bEQw7UEBUVAuLGHH+UwMlbXtMS+ufiSlwy02Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1693841564; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WnMfo/YdMJSmNHHjRE4rIpFGDmSIEwOltYFTzlE5W2s=; b=oL1++Tjy5VmwMMirG2NSkF0viKYtf6lXFisNgP+SHvxYy16337DXhoFeigLMMyGv2vGayW I5RVmP9twiaWKW6MPXR1pfXrm8QTiC+c49WKUmOW7iWM1MzVI2RXTFj+IsiytYtXLDzujR WXZQWbsq3+C4yxioXFUfdPVPCxDI98KF4XjPHlAvwKPz21DsoIfy2Y8jb0Xyd5FZj5iaC7 W9LnXlpbm6VxLqn0ma6gP6QeehLboLzYPqL1bvMZZiAbgspDxPTX04J4ZiXdUf4NkjeMwL Xu5T/m2pKGFmKfDtIdMracxO0y6zC4cQqANqTYOVhHtv1UgoAs529fvfITBulw== Received: from [10.9.4.95] (unknown [209.182.120.176]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: kevans/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4RfXhC4BTSzrH9; Mon, 4 Sep 2023 15:32:43 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Message-ID: Date: Mon, 4 Sep 2023 10:32:41 -0500 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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: FreeBSD arm64 Azure panic during reboot in add_route Content-Language: en-US To: Souradeep Chakrabarti , "freebsd-hackers@FreeBSD.org" , "freebsd-arm@FreeBSD.org" Cc: Wei Hu References: From: Kyle Evans In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 9/4/23 05:13, Souradeep Chakrabarti wrote: > Hi > I am working on bringing FreeBSD on Azure ARM64. When I am rebooting the FreeBSD arm64 in Azure public preview, > we are hitting following panic sometime for page fault: > db_trace_self_wrapper() at db_trace_self_wrapper+0x30 > vpanic() at vpanic+0x13c > panic() at panic+0x44 > data_abort() at data_abort+0x30c > handle_el1h_sync() at handle_el1h_sync+0x14 > --- exception, esr 0x8600000e > (null)() at 0xffffa0000c93bb00 > add_route() at add_route+0xc4 > add_route_flags() at add_route_flags+0x1b0 > rib_add_route() at rib_add_route+0x324 > ifa_maintain_loopback_route() at ifa_maintain_loopback_route+0xf4 > in6_update_ifa() at in6_update_ifa+0x994 > in6_ifattach() at in6_ifattach+0x1bc > in6_if_up() at in6_if_up+0x90 > if_up() at if_up+0xd8 > ifhwioctl() at ifhwioctl+0xb7c > ifioctl() at ifioctl+0x860 > kern_ioctl() at kern_ioctl+0x2dc > sys_ioctl() at sys_ioctl+0x118 > do_el0_sync() at do_el0_sync+0x520 > handle_el0_sync() at handle_el0_sync+0x44 > > The panic is coming when add_route is called for loopback interface ipv6 attachment. > Upon more investigating it looks like the panic happens in rib_notify() . > > Please let me know how to debug it further to find the RC. > I have already opened a bug to track it : https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272666 > Hi, I note that Andy has an unanswered question in that PR (comment #9) from 2023/08/14. Do you have a coredump from this that you can poke around in easily with kgdb? Thanks, Kyle Evans