From nobody Fri Dec 9 19:53:17 2022 X-Original-To: freebsd-questions@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 4NTMFw4L2Sz4k8j5 for ; Fri, 9 Dec 2022 19:55:48 +0000 (UTC) (envelope-from anubhav@hawaii.edu) Received: from mail-yw1-x1132.google.com (mail-yw1-x1132.google.com [IPv6:2607:f8b0:4864:20::1132]) (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 4NTMFv2CxHz3phn for ; Fri, 9 Dec 2022 19:55:47 +0000 (UTC) (envelope-from anubhav@hawaii.edu) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=hawaii.edu header.s=google header.b=H5YOlnyp; spf=pass (mx1.freebsd.org: domain of anubhav@hawaii.edu designates 2607:f8b0:4864:20::1132 as permitted sender) smtp.mailfrom=anubhav@hawaii.edu; dmarc=pass (policy=none) header.from=hawaii.edu Received: by mail-yw1-x1132.google.com with SMTP id 00721157ae682-3b10392c064so66276017b3.0 for ; Fri, 09 Dec 2022 11:55:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hawaii.edu; s=google; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=hsrU+gyDAfmwXAwcUSqgu5XiwLwnL60fFDc6vRULxBQ=; b=H5YOlnypzGcv06/z48A67bn0Sz5sGPr+wU+rjyGZ/MNm+D6E6eP9oxFAbcD6vuSr2Z W0hb2GtUREk7S9KrZjyVTFc2zFOlsZMpHto/X4s1dFSIQFFtid+hj8Eh8qi8nSgxEQrh z3xd3BddnaOojxkjkHw7+t88kOhs+upJ7qqL4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=hsrU+gyDAfmwXAwcUSqgu5XiwLwnL60fFDc6vRULxBQ=; b=VeBNwNufsMXxtfIcDqzUyyEl1ZeGnXJPSMc19jWRzi9TS6q+Hz0nlL8PIHvsc38ZXF 1Ho4SYaPiQXgEgLgiVAlMGJ7WMHGZFC8OmsU2L3hVV/++y0fJMIeGeKVk4KTgA8bd3/d munUU942sdMFbXR37iuo69udaIFO8FWg1sh8jqZKZIX2GvPderZhce33xQOI8rGHfpQD FPivPCf5kM4X6wxpVfC/Dv+LE3yoRnY8k1bpfSbtmFQPdapDgRJ/EhV8B0i5bckCL2QT GW79BFBJ0EhGncayOg5SK+/VlVJ7GsT6NLc+eEYbtOAsoj9Fak0Q7hsDV3qgKPm9KlpU u64g== X-Gm-Message-State: ANoB5pn42y+prPZej3R87OifGOKRHfLCWUJuCfsEYFvQgptWd43eBc7A oal0dIkrBbRf10kZpFGTHgGv0Pq/R4eXVyK/tOUY60fnkP811OYiSEYXGGCApS61luxXJhR/a+l SDJNof/NTswMisYlM1kInndK10aPuOwfOvCYJBWGH6mKolJzWDQRv63OQeK+e7hcqeh93QsuXhS uAGqaghIIqv2bBdR0OLxIeY7jLaefXTqU87JCBAdzW X-Google-Smtp-Source: AA0mqf7SdWYHkct/pMq+2PZN8IsnXanouElsdS6dLFSsmb9+XSpYn+GbUBH1Mh3Eb1ufa3skKZNX+9CTfW4lN3sgD1M= X-Received: by 2002:a05:690c:ec6:b0:376:f7e2:4b12 with SMTP id cs6-20020a05690c0ec600b00376f7e24b12mr6053254ywb.0.1670615746189; Fri, 09 Dec 2022 11:55:46 -0800 (PST) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: "Anubhav/FreeBSD" Date: Fri, 9 Dec 2022 09:53:17 -1000 Message-ID: Subject: Re: After 13.1 install, "panic: AP #1 (PHY #1) failed!" with SuperMicro X10SRL-F motherboard To: freebsd-questions@freebsd.org Content-Type: multipart/alternative; boundary="0000000000001bb91205ef6a8ade" X-Spamd-Result: default: False [-5.00 / 15.00]; DWL_DNSWL_LOW(-1.00)[hawaii.edu:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[hawaii.edu,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[hawaii.edu:s=google]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::1132:from]; ARC_NA(0.00)[]; SUBJECT_HAS_EXCLAIM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[hawaii.edu:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; TAGGED_FROM(0.00)[freebsd]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4NTMFv2CxHz3phn X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N --0000000000001bb91205ef6a8ade Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable (Please email me too when you reply.) On Fri, Dec 9, 2022 at 9:35 AM Anubhav/FreeBSD wrote: > The computer server with ... > > SuperMicro X10SRL-F motherboard (LGA 2011-V3, C612 chipset), > Intel Xeon E5-1620 V3 CPU > > ... was working just fine with FreeBSD 12.x & 13.0. 13.0 was > installed from scratch with ZFS on root. > > Two days ago I updated the OS to 13.1-p5 in a new boot environment > ("freebsd-update -r 13.1-RELEASE upgrade"; "freebsd-update install"; > reboot; "freebsd-update install"). I did so over ssh. > > ... > After reboot of 13.1-p5, a "panic" happens all the 3-4 times I tried ... > > (transcribed from the photo of the screen after booting in verbose mode) > SMP: Added CPU 1 (AP) > MADT: Found CPU APIC ID 3 ACPI ID 3: enabled > SMP: Added CPU 3 (AP) > MADT: Found CPU APIC ID 5 ACPI ID 5: enabled > SMP: Added CPU 5 (AP) > MADT: Found CPU APIC ID 7 ACPI ID 7: enabled > SMP: Added CPU 7 (AP) > Event timer "LAPIC" quality 600 > LAPIC: ipi_wait() us multiplier 64 (r 5400080 tsc 3500095930) > ACPI APIC Table: > Package ID shift: 4 > L3 cache shift: 4 > L2 cache shift: 1 > L1 cache shift: 1 > Core ID shift: 1 > AP boot address: 0x98000 > panic: AP #1 (PHY #1) failed! > cpuid =3D 0 > time =3D 1 > KDB: stack backtrace > #0 0xffffffff80c694a5 at kdb_backtrace+0x65 > #1 0xffffffff80c1bb5f at vpanic+0x17f > #2 0xffffffff80c1b983 at panic+0x43 > #3 0xffffffff81093633 at native_start_all_aps+0x633 > #4 0xffffffff81092ce1 at cpu_mp_start+0x1a1 > #5 0xffffffff80c7c32a at mp_start+0x9a > #6 0xffffffff80ba970f at mi_startup+0xdf > #7 0xffffffff80385022 at btext+0x22 > Uptime: 1s > > ... I wonder if "3.0a" c 2018 update could be helpful ... https://www.supermicro.com/en/support/resources/downloadcenter/firmware/MBD= -X10SRL-F/BIOS https://www.supermicro.com/Bios/softfiles/14139/X10SRL-F_BIOS_3.4_release_n= otes.pdf (The direct PDF URL does not work; need to go to the "Download" page first.) " 1. Updated CPU microcode to address =E2=80=98Spectre=E2=80=99 variant 2 (= CVE 2017-5715) security issue. 2. Updated SATA RAID OPROM/EFI driver to RSTe PreOS v4.7.0.1014. 3. Updated Intel Server Platform Services 3.1.3.50 for Grantley Refresh Platforms. 4. Removed support for using Ctrl+home to trigger recovery. 5. Changed Memory correctable threshold to 100 and enabled Cloaking for Broadwell CPU E5-26xx SKU. 6. Changed BIOS revision to 3.0a. 7. Updated Broadwell-EP RC 4.3.0 PLR10 release. 8. Removed the "P1" string when Memory error occurs on UP server. 9. Corrected POST diagnostic signOn string. 10. Patched Micron Z11C DIMM to improve stability. 11. Changed tCCD_L Relaxation default to 1 and changed string from Enabled to Auto. 12. Appended VPD - VB tag in VPD-W Tag(0x91) area. 13. Updated new MRC error log definition. 14. Added Intel SPI vulnerability patch for Grantley. 15. Added "SMBIOS Preservation" Enabled/Disabled item for flash recovery. 16. Enhanced SMC Recovery Flash Boot Block feature. 17. Displayed setup item "ACS Control" to Enable/Disable PCIe Access Control Services Extended Capability. 18. Added BBS reset function to SmcOobLoadBiosDefault(). 19. Added SumBbsSupportFlag into DAT file. 20. Implemented SMC Recovery Flash Boot Block feature. 21. Fixed issue of SUM TC306 and TC317 failing in certain configuration cases. 22. Fixed problem of system hanging after Watch Dog function is enabled and then BIOS is updated. 23. Fixed incorrect memory error location on UP server. 24. Fixed problem of system hanging on POST code 0xB2. 25. Fixed problem of system resetting or hanging after Watch Dog function is enabled and then BIOS is updated. 26. Fixed inability to get correct Memory CECC DIMM location via SD5. 27. Fixed problem of incorrect PCI slot number showing on Legacy/UEFI mode. " ... Also, how does one go about flashing the BIOS: boot with copy of the files on a USB flash disk? - Anubhav --0000000000001bb91205ef6a8ade Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 
(Please email me too when=
 you reply.)

On Fri, Dec = 9, 2022 at 9:35 AM Anubhav/FreeBSD wrote:
The computer server with =
...

SuperMicro X10SRL-F motherboard (LGA 2011-V3, C612 chipset),
Intel Xeon E5-1620 V3 CPU

... was working just fine with FreeBSD 12.x & 13.0. 13.0 was
installed from scratch with ZFS on root.

Two days ago I updated the OS to 13.1-p5 in a new boot environment
("freebsd-update -r 13.1-RELEASE upgrade"; "freebsd-update i=
nstall";
reboot; "freebsd-update install"). I did so over ssh.
=
...=C2=A0
After reboot of 13.1-p5, a "=
;panic" happens all the 3-4 times I tried ...

(transcribed from the photo of the screen after booting in verbose mode)
SMP: Added CPU 1 (AP)
MADT: Found CPU APIC ID 3 ACPI ID 3: enabled
SMP: Added CPU 3 (AP)
MADT: Found CPU APIC ID 5 ACPI ID 5: enabled
SMP: Added CPU 5 (AP)
MADT: Found CPU APIC ID 7 ACPI ID 7: enabled
SMP: Added CPU 7 (AP)
Event timer "LAPIC" quality 600
LAPIC: ipi_wait() us multiplier 64 (r 5400080 tsc 3500095930)
ACPI APIC Table: <SUPERM SMCI--MB>
Package ID shift: 4
L3 cache shift: 4
L2 cache shift: 1
L1 cache shift: 1
Core ID shift: 1
AP boot address: 0x98000
panic: AP #1 (PHY #1) failed!
cpuid =3D 0
time =3D 1
KDB: stack backtrace
#0 0xffffffff80c694a5 at kdb_backtrace+0x65
#1 0xffffffff80c1bb5f at vpanic+0x17f
#2 0xffffffff80c1b983 at panic+0x43
#3 0xffffffff81093633 at native_start_all_aps+0x633
#4 0xffffffff81092ce1 at cpu_mp_start+0x1a1
#5 0xffffffff80c7c32a at mp_start+0x9a
#6 0xffffffff80ba970f at mi_startup+0xdf
#7 0xffffffff80385022 at btext+0x22
Uptime: 1s
...=C2=A0

I wonder if "3= .0a" c 2018 update could be helpful ...

=C2=A0 https://w= ww.supermicro.com/en/support/resources/downloadcenter/firmware/MBD-X10SRL-F= /BIOS
=C2=A0 https://www.supermicro.com/Bios/softfiles/1413= 9/X10SRL-F_BIOS_3.4_release_notes.pdf
=C2=A0 (The direct PDF URL does not work; = need to go to the "Download" page
=C2=A0=C2=A0 first.)

"
=C2=A0 1. Updated CPU mi= crocode to address =E2=80=98Spectre=E2=80=99 variant 2 (CVE
=C2=A0 =C2= =A0 =C2=A0 2017-5715) security issue.
=C2=A0 2. Updated SATA RAID OPROM/= EFI driver to RSTe PreOS v4.7.0.1014.
=C2=A0 3. Updated Intel Server Pla= tform Services 3.1.3.50 for Grantley
=C2=A0 =C2=A0 =C2=A0 Refresh Platfo= rms.
=C2=A0 4. Removed support for using Ctrl+home to trigger recovery.<= br>=C2=A0 5. Changed Memory correctable threshold to 100 and enabled Cloaki= ng
=C2=A0 =C2=A0 =C2=A0 for Broadwell CPU E5-26xx SKU.
=C2=A0 6. Chan= ged BIOS revision to 3.0a.
=C2=A0 7. Updated Broadwell-EP RC 4.3.0 PLR10= release.
=C2=A0 8. Removed the "P1" string when Memory error = occurs on UP server.
=C2=A0 9. Corrected POST diagnostic signOn string.<= br>=C2=A0 10. Patched Micron Z11C DIMM to improve stability.
=C2=A0 11. = Changed tCCD_L Relaxation default to 1 and changed string from
=C2=A0 = =C2=A0 =C2=A0 Enabled to Auto.
=C2=A0 12. Appended VPD - VB tag in VPD-W= Tag(0x91) area.
=C2=A0 13. Updated new MRC error log definition.
=C2= =A0 14. Added Intel SPI vulnerability patch for Grantley.
=C2=A0 15. Add= ed "SMBIOS Preservation" Enabled/Disabled item for flash
=C2= =A0 =C2=A0 =C2=A0 recovery.
=C2=A0 16. Enhanced SMC Recovery Flash Boot = Block feature.
=C2=A0 17. Displayed setup item "ACS Control" t= o Enable/Disable PCIe Access
=C2=A0 =C2=A0 =C2=A0 Control Services Exten= ded Capability.
=C2=A0 18. Added BBS reset function to SmcOobLoadBiosDef= ault().
=C2=A0 19. Added SumBbsSupportFlag into DAT file.
=C2=A0 20. = Implemented SMC Recovery Flash Boot Block feature.
=C2=A0 21. Fixed issu= e of SUM TC306 and TC317 failing in certain
=C2=A0 =C2=A0 =C2=A0 configu= ration cases.
=C2=A0 22. Fixed problem of system hanging after Watch Dog= function is
=C2=A0 =C2=A0 =C2=A0 enabled and then BIOS is updated.
= =C2=A0 23. Fixed incorrect memory error location on UP server.
=C2=A0 24= . Fixed problem of system hanging on POST code 0xB2.
=C2=A0 25. Fixed pr= oblem of system resetting or hanging after Watch Dog
=C2=A0 =C2=A0 =C2= =A0 function is enabled and then BIOS is updated.
=C2=A0 26. Fixed inabi= lity to get correct Memory CECC DIMM location via SD5.
=C2=A0 27. Fixed = problem of incorrect PCI slot number showing on
=C2=A0 =C2=A0 =C2=A0 Leg= acy/UEFI mode.
"

... Also, how does one go about flashing the BIOS: boot with copy o= f
th= e files on a USB flash disk?


- Anubhav

--0000000000001bb91205ef6a8ade--