From nobody Wed Nov 17 16:40:36 2021 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 2754C1854E9E for ; Wed, 17 Nov 2021 16:40:50 +0000 (UTC) (envelope-from m.efe@mailbox.org) Received: from mout-p-102.mailbox.org (mout-p-102.mailbox.org [80.241.56.152]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4HvTFW5xmzz4ZBf for ; Wed, 17 Nov 2021 16:40:47 +0000 (UTC) (envelope-from m.efe@mailbox.org) Received: from smtp202.mailbox.org (smtp202.mailbox.org [IPv6:2001:67c:2050:105:465:1:4:0]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-102.mailbox.org (Postfix) with ESMTPS id 4HvTFN1XNSzQkBd for ; Wed, 17 Nov 2021 17:40:40 +0100 (CET) X-Virus-Scanned: amavisd-new at heinlein-support.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailbox.org; s=mail20150812; t=1637167238; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=jqnOj6qaB2J9m1vpBqvKix3kASrYttMR8UdspFi7HuA=; b=LpZJc5s9mGlXkhU/Ihh124JpHv9O6NTjPncpvA/XDJ9e2YinDYWA15h88zW6ylLHr7VZ9y MEMecrmOn6y/L9YzXGWJFwZyiCj3Muj3UcvqHCRAAnkvLW5J3lOF0WAK6hiZb1MWVdbyvg IfF6KiOi/+OOr3sKJSo0EiorLekGSTv/JPHx/KVNode5Q1Xfl0hhbFtusvlSak8oVRrP2m onys4UF4BXUIZ5nabU7pW8MWJpiyuvtPGH3FSq0VVqHT243bkxPfBEU1l1nq53Ggn9Tghj HeottpyXWSw0gW2ROnk5blBcq2q3Dhf0/mtYAcrc61a00iEHc0q6+oTABdBCMA== Date: Wed, 17 Nov 2021 17:40:36 +0100 (CET) To: "freebsd-arm@freebsd.org" Message-ID: <136528742.227697.1637167236577@office.mailbox.org> Subject: Re: RPI CM4 boot kernel panic 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 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 Importance: Normal X-Rspamd-Queue-Id: 4HvTFW5xmzz4ZBf X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=mailbox.org header.s=mail20150812 header.b=LpZJc5s9; dmarc=pass (policy=reject) header.from=mailbox.org; spf=pass (mx1.freebsd.org: domain of m.efe@mailbox.org designates 80.241.56.152 as permitted sender) smtp.mailfrom=m.efe@mailbox.org X-Spamd-Result: default: False [-3.08 / 15.00]; FAKE_REPLY(1.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[mailbox.org:s=mail20150812]; RCVD_IN_DNSWL_LOW(-0.10)[80.241.56.152:from]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:80.241.56.0/21]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RWL_MAILSPIKE_POSSIBLE(0.00)[80.241.56.152:from]; MID_RHS_MATCH_FROMTLD(0.00)[]; DKIM_TRACE(0.00)[mailbox.org:+]; DMARC_POLICY_ALLOW(-0.50)[mailbox.org,reject]; HAS_X_PRIO_THREE(0.00)[3]; NEURAL_HAM_SHORT(-0.98)[-0.981]; TO_DN_EQ_ADDR_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:199118, ipnet:80.241.56.0/21, country:DE]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[mailbox.org:dkim] Reply-To: m.efe@mailbox.org From: M. Efe via freebsd-arm X-Original-From: M. Efe X-ThisMailContainsUnwantedMimeParts: N I don't see the patch or dmesg log here, but can confirm that the issue still persists with the latest FreeBSD 13-STABLE snapshot. devmatch_enable="NO" in /etc/rc.conf indeed allows you to boot the device, but only as long as no PCIe device is connected. I tested with different cards (I350-T4 with a Riser 1x to 16x cable, VL805 USB 3.0 Card) and ran into kernel panics every time I tried to boot. Just calling devmatch also results in a kernel panic. Nevertheless, my device was running quite stable for 2 days building world, kernel and ports without any brake :) --- original message --- There's something wrong with rman and libdevinfo, see attached patch and dmesg. --- end of original message --- Do you mind sharing the patch? Btw., I assume you're using the standard IO board, right?