From nobody Mon May 15 13:09:53 2023 X-Original-To: freebsd-current@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 4QKfqb0x6hz4BbNF for ; Mon, 15 May 2023 13:10:19 +0000 (UTC) (envelope-from fbl@aoek.com) Received: from mail.yourbox.net (mail.yourbox.net [IPv6:2001:41d0:1:767d::1]) (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 (2048 bits) client-digest SHA256) (Client CN "mail.yourbox.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QKfqX2g9Qz4NF3 for ; Mon, 15 May 2023 13:10:16 +0000 (UTC) (envelope-from fbl@aoek.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aoek.com header.s=mailbox header.b="c9hyR5/q"; spf=pass (mx1.freebsd.org: domain of fbl@aoek.com designates 2001:41d0:1:767d::1 as permitted sender) smtp.mailfrom=fbl@aoek.com; dmarc=pass (policy=reject) header.from=aoek.com Received: from mail.yourbox.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by mail.yourbox.net (8.17.1/8.17.1) with ESMTP id 34FD9wLe050993; Mon, 15 May 2023 15:09:58 +0200 (CEST) (envelope-from fbl@aoek.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=aoek.com; s=mailbox; t=1684156198; bh=MN27fpagKNpZ1Sqwwhb3HDYBQwdTX7XFHImkwbI0SF4=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=c9hyR5/qIrDJO0RPn5oBykk9WZjO/DQOHJIVpQ627NrC8UOphtU1Z8Qz46mTPuFyf SwUtRNMJ6zM3X+rQ7PKRQK4xZIyWh+jIfb9D0rdisEAN+yplTUfBCkfy1nJXO+72iv xRzIwiFkPYmCON+j/WC3o0GcKKmV81GX3rxJOzCOAhk7cjku0s0tHmuq+CdT8dArSn IEa32aBUAPZ/5luVxYLVwX7E2cOUFUbuKJzVxz8lpNheifX7/13DL75LtLH2FdO3Sj N8pf8zzOf7Cbs7EZl7PmpLSZA4oVWG4x1msPGi9j+Fq0SCor/A4rA1G6uY3EPfU3yR zLcYRxy8UVoAQ== List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Mon, 15 May 2023 15:09:53 +0200 From: =?UTF-8?Q?Jos=C3=A9_P=C3=A9rez?= To: Rebecca Cran Cc: Current FreeBSD Subject: Re: 20230504 -CURRENT snapshot panics during install at zfs probing In-Reply-To: References: Message-ID: <56da7c27b99ae6bc0ff3880f3cff5733@mail.yourbox.net> X-Sender: fbl@aoek.com User-Agent: Roundcube Webmail/1.2.0 X-Spamd-Result: default: False [-3.17 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; R_MIXED_CHARSET(0.83)[subject]; DMARC_POLICY_ALLOW(-0.50)[aoek.com,reject]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[aoek.com:s=mailbox]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; BLOCKLISTDE_FAIL(0.00)[2001:41d0:1:767d::1:server fail]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[aoek.com:+]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4QKfqX2g9Qz4NF3 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N El 2023-05-05 13:31, Rebecca Cran escribió: > I also tried FreeBSD 13.2 and it's unhappy too, and ends up panicing > and rebooting when trying to restart the installer after it segfaults. > So it's apparently _not_ a new problem. > > I'm guessing there's something about my disks that's causing memory > corruption. The only thing that's changed recently is installing > Windows Server 2022 on a different disk. > > If I disable the mrsas controller, installation proceeds. > > > -- > Rebecca Cran > > > On 5/4/23 19:02, Rebecca Cran wrote: >> I'm seeing a panic during install during the zfs probing on the >> 14-CURRENT 20230504 amd64 snapshot on a PowerEdge R7525 dual-EPYC >> system. >> >> I haven't submitted a bug report for a while, so let me know what >> other information is needed. >> >> >> Unfortunately the stack backtrace looks useless: Hi, I recall exepriencing a similar issue with a SuperMicro server and I think I worked this around by adding hw.mfi.mrsas_enable="1" to /boot/device.hints in order to have FreeBSD booting from the SAS disks. Unfortunately I do not have access to that hardware anymore (it is running AnotherOS and cannot be taken out of production). I still recommend you do open a bug with the details you have so far, having FreeBSD on server with SAS disks is not a sin ;) and software causing memory corruption shall be fixed anyways. -- José Pérez