From nobody Mon Nov 28 21:17:32 2022 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 4NLfKg6CsRz4j2Sg for ; Mon, 28 Nov 2022 21:50:47 +0000 (UTC) (envelope-from editor@callfortesting.org) Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NLfKg14t1z3hv2 for ; Mon, 28 Nov 2022 21:50:47 +0000 (UTC) (envelope-from editor@callfortesting.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=callfortesting-org.20210112.gappssmtp.com header.s=20210112 header.b=ZReYds8f; spf=none (mx1.freebsd.org: domain of editor@callfortesting.org has no SPF policy when checking 2607:f8b0:4864:20::102c) smtp.mailfrom=editor@callfortesting.org; dmarc=none Received: by mail-pj1-x102c.google.com with SMTP id b13-20020a17090a5a0d00b0021906102d05so9982561pjd.5 for ; Mon, 28 Nov 2022 13:50:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=callfortesting-org.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:subject:from:to:content-language :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=nAP0EkkDPEKVpaDg2lF3iA42V474sqYqLsaY/J/FHMM=; b=ZReYds8fLnPxbgymBLhjQZKZG7jcdqnOgs6WCpfirFeXcDV1uK15bBs9arKIUqdRev N++rxwVtRZggw1VPAsExWBD+zFIQVOGbIl0MD5J5aQJB8DCqSRsJSAlTaVcxdtRNvos3 7JgL3oDqguQY6gjEjUxNajZShUTsosVLYo1dOQhHQYJ5VYenrLBkyhaYNRALZnZAdvtS fOkoCUGs2PHPlPyTP+nwuigmD77aGu6/E1yKtMQPB0g85kfpngzAxoFBoWEvp3N5FM8g Ub2t2/PqxQsrcYe7U+dG43yL70lSFehl/7WswbWSNGMBiUQwNxG32eRR0SRUF8qrtQoB 9BXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:subject:from:to:content-language :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=nAP0EkkDPEKVpaDg2lF3iA42V474sqYqLsaY/J/FHMM=; b=G+UO9b5p8u/gIT5jRn88XWHXtwN1T0Z7n8flyAk2qzNQZpvD1dP5PSF5VVG17RktSF 6ig2d4yV3o2p3Fq7YAHMIRK5m6AlTTSy4IoNaj14596902d9Zp/9KsQeqgTzNWZHZKbs jkGoRVBORDX0fsYyvQL+xay1T9cqkGIvlme4FObTvWcS12Hkz8YHC6vRPhzNSwBgg6QQ gDpM4Uq2pRv+pjWqTyS9n/zBCAKPU8dioAivhW8YSUvEi+PiIlBqqqs+TS4V9B9SCssI o2/4gNAiOpqe2QYDAwOgVkbFaGvw6hB9yJyyDAIl2bmXwtcLS6MP+Bc/liRayRi7DQ+v tpZQ== X-Gm-Message-State: ANoB5pnHSnTazFkbeZLVDOt/GmXxOItY5rMVKAHnsfhLep79E27umLQ0 N6TsreespTzloLq+z1JcQgL8+UhU5eViG9DT X-Google-Smtp-Source: AA0mqf6YkQzeIkRNr0L2p+b7UrQKWePXv10W148TW0SwoRTNTGi7Jmsnb6Wu6Deih3JQG8Cvq3s0dQ== X-Received: by 2002:a17:90b:2d8b:b0:202:f88d:587 with SMTP id sj11-20020a17090b2d8b00b00202f88d0587mr57821821pjb.232.1669672245545; Mon, 28 Nov 2022 13:50:45 -0800 (PST) Received: from [10.0.0.236] (c-73-157-223-253.hsd1.or.comcast.net. [73.157.223.253]) by smtp.gmail.com with ESMTPSA id q18-20020a170902f79200b0016cf3f124e1sm9330189pln.234.2022.11.28.13.50.45 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 28 Nov 2022 13:50:45 -0800 (PST) Message-ID: Date: Mon, 28 Nov 2022 13:17:32 -0800 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 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Content-Language: en-US To: freebsd-current@freebsd.org From: Michael Dexter Subject: smartpqi0 "panic: Segment size is not aligned" Related panic on savecore? Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-2.30 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.997]; R_DKIM_ALLOW(-0.20)[callfortesting-org.20210112.gappssmtp.com:s=20210112]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::102c:from]; R_SPF_NA(0.00)[no SPF record]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; DKIM_TRACE(0.00)[callfortesting-org.20210112.gappssmtp.com:+]; RCVD_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DMARC_NA(0.00)[callfortesting.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4NLfKg14t1z3hv2 X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N The HPE P408i-a SR Gen10 3.00/smartpqi(4) on an HP DL325 EYPC system worked well under 13.* and a SATA SSD but is providing odd behavior under the 14-CURRENT 2022-11-23 RE snapshot. The dmesg is blown with this incrementing error: ... (probe0:smartpqi0:0:582:0): Down reving Protocol Version from 6 to 2? (probe1:smartpqi0:0:583:0): Down reving Protocol Version from 6 to 2? (probe0:smartpqi0:0:584:0): Down reving Protocol Version from 6 to 2? ... (probe0:smartpqi0:0:1088:2): Down reving Protocol Version from 6 to 5? pass0 at smartpqi0 bus 0 scbus0 target 64 lun 0 pass0: Fixed Enclosure Services SPC-3 SCSI device (quiets down) dd'ing the 2022-11-23 Release Engineering VM raw snapshot to a device boots fine via USB and performs a growfs but booting to the HBA results in a panic when savecore it run, reporting: panic: Segment size is not aligned Workaround: Set savecore_enable="NO" in rc.conf before booting. Reproduction: service savecore onestart Cleanup: fsck / in single user mode and disable savecore as needed. Possibly related? Open (note savecore): https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240145 Resolved with the same "Segment size is not aligned" panic: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259541 https://reviews.freebsd.org/D30182 Should I update that second PR? Have any suggestions for verifying the issue? All the best, Michael