From nobody Fri Jul 05 11:18:49 2024 X-Original-To: bugs@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 4WFrcV0VWHz5P52l for ; Fri, 05 Jul 2024 11:18:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WFrcT4p4nz51ht for ; Fri, 5 Jul 2024 11:18:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1720178329; a=rsa-sha256; cv=none; b=VZ88Bl/mRazbBm2jNMdHs4Am2KxzP76GVjB5I2Nh8XkEItRSsTfrN3cJilnvyxuIkhuqZP 3QXQ/G0jY6qZLPWUsloT6JeoXTyoHJIMONW64koDgGqEFHWSP0IdLIKHKZV/KJJPbqsYQ0 lA1bDb+piaMrJz+CAv2XpLPiYBfdN2luDUEpMKdUHxOBfpLogjwhDUUPJRAc9jO5Qltl+K XXMGRXmIRkJbQ1suJKWJ7Oc2BBKzc3Ge+WznDfSuawQWZLvPI2/2EaxJAHekcI/uTO/86f cEwdihWUBi1zy0dTFXEXDsFppHC53qW3HKnjUGlMqUoYKhVz3/PEnwjJc2dY3w== 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=1720178329; 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=T73mSDcWYyWfwKk2ZLe+PeGkWX0Bqp5PL3uyJzEfyw0=; b=TMFbZSXbS0Gp5oMDxErAts9+Ke/abuww1c7VKYV5w6iMBpNOtqyKKfHx9pZq3eNqMPTbQ7 SsWkdOKtt7hfBpl9Vu9saakmm5hlp7dSIvm81GY8WE5BoTHwGI+9OAF988sQjZYvYdS+QW qy7lpJY+q5/KAQN0e8BVLFw7L/hwEJuWbQHs9x0IB0STb6aHNoGpyQChca698qcZCMm6qd 7yYmUM7vHCnlQLgnvxXsH73J/PfN+KS+5cSfDGVTy4ACvSxtXhT2grxL9UtR3KF1g9AWrk sZ33nuI3Y44sKWDuv6NC8pfZq6ldSwVAGbXoVKvss/tUJLzHBpE8UYLwae9mfw== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4WFrcT46DkzvLC for ; Fri, 5 Jul 2024 11:18:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 465BIn6a029383 for ; Fri, 5 Jul 2024 11:18:49 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 465BIn16029382 for bugs@FreeBSD.org; Fri, 5 Jul 2024 11:18:49 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 280140] mpr max_chains causing boot failure when zfs module is loaded during boot Date: Fri, 05 Jul 2024 11:18:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 14.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: bsd.m0osk@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D280140 Bug ID: 280140 Summary: mpr max_chains causing boot failure when zfs module is loaded during boot Product: Base System Version: 14.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: bsd.m0osk@gmail.com Created attachment 251883 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D251883&action= =3Dedit screenshot showing mpr out of chain frames immediately after zfs is loaded Server Hardware Model: PowerEdge R760xd2=20 RAM: 256GB Disk Controller: Broadcom / LSI HBA355i Adapter Symptom(s): during boot, mpr runs out of chain frames as soon as zfs module is loaded in the kernel and thereby fails to boot into OS Details: If I boot from the installation disk, and during boot set hw.mpr.max_chains=3D32768 and dev.mpr.0.max_chains=3D32768 then I can boot = to installer and install the OS (either ZFS or UFS) However, once I have setup a zfs-on-root system, the server fails to boot on subsequent attempts (from the installed OS) irrespective of any number/value set for max_chains, it always complains about running out of chain frames. = This happens immediately after loading the ZFS module (feature support 5000). I have tried all possible values for max_chains between 8192 till 1048576, = none of them worked, and same error message about running out of chain frames.=20 I have tried to boot by disabling zfs on the installed system, that fails a= nd goes to mountroot (obviously!). Since I am not aware of any other way to lo= ad the zfs module between mountroot and *right after* mpr has settled down, I = do not know what other test can be done to confirm or get more details and possibly fix this. What has worked so far: I can boot into the installer and install a root-on-UFS system. As long as = I am not loading the zfs module during boot (either manually or via /boot/loader.conf), the system boots without any problem. I can have zfs pools/datasets by having zfs and zfsd running from rc.conf (it loads the mo= dule after the system has settled down) So, in a way I have a relatively functional/semi-stable system that I can continue to work with. But I would very much like to have the root on zfs. Curious facts: I have an almost-identical server, difference being the other one has 512GB= ram and does not have some of the ethernet cards that are in this server, and t= hat other server is running with FreeBSD 14.1 with root-on-zfs. The other server being on production I cannot run any tests on it now. So, for comparison, I disabled the additional network cards on the current partially working syst= em, and tried to boot into it. Same error -- running out of chain frames. The option to put root-on-UFS works anyway. --=20 You are receiving this mail because: You are the assignee for the bug.=