Date: Tue, 13 Dec 2022 10:35:24 -1000 From: "Anubhav (Re: FreeBSD)" <anubhav+freebsd@hawaii.edu> To: freebsd-questions@freebsd.org Subject: Re: After 13.1 install, "panic: AP #1 (PHY #1) failed!" with SuperMicro X10SRL-F motherboard Message-ID: <CAPD2KN-c_=56NvoOvHHUhr=pxKsjKrfDUkVepsZ25358T10mMg@mail.gmail.com> In-Reply-To: <CAPD2KN-KZcpWAAbnq62r7JhPOKv1nOQctbN24EKqp00pjzqWDw@mail.gmail.com> References: <CAPD2KN-KZcpWAAbnq62r7JhPOKv1nOQctbN24EKqp00pjzqWDw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000efc1c705efbb98f1
Content-Type: text/plain; charset="UTF-8"
(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 a day, I could not connect to the computer via ssh. When I checked,
> lots of error messages from sshd were *flying* on the console (failed to
> take a photo). I could not do anything on the console. (The computer is
> connected to video & keyboard via software KVM; there is no physical serial
> connection.)
>
> 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 = 0
> time = 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
>
>
> ... What is going on here, or what had happened with 13.1 install
> that the machine panics?
>
> Booting with any of 13.0-p1[13] boot environments makes
> no difference.
>
> ...
After removing the machine from the rack (included disconnection
of RaidMachine 24-bay disk enclosure from the LSI HBA card
installed in the machine), it booted right up (with already
installed FreeBSD 13.1-p5 on the internal disk) as if nothing
had happened! There was no panic or any "AP #1 (PHY #1)
failed!"-like messages.
How? Why?
If the machine still had panicked (after removal from the rack),
then I could have tried ...
- updating the BIOS;
- booting from 13.[01] image from a USB flash stick;
- installing 13.[01] from scratch.
Now, I do not know how much I can trust the machine to
not fail (panic again on a reboot).
- Anubhav
--000000000000efc1c705efbb98f1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:monospace">
<pre id=3D"m_8742427158830638314m_5045518395078331800m_-4675011571234176461=
gmail-raw_message_text"><span class=3D"gmail_default" style=3D"font-family:=
monospace"></span>(Please email me too when you reply.)</pre>
</div><div class=3D"gmail_default" style=3D"font-family:monospace"><br></di=
v><div class=3D"gmail_default" style=3D"font-family:monospace">On Fri, Dec =
9, 2022 at 9:35 AM Anubhav/FreeBSD wrote:</div></div><div class=3D"gmail_qu=
ote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><di=
v style=3D"font-family:monospace">
<pre id=3D"m_8742427158830638314m_5045518395078331800m_-4675011571234176461=
gmail-raw_message_text"><span class=3D"gmail_default" style=3D"font-family:=
monospace"></span>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.
After a day, I could not connect to the computer via ssh. When I checked,
lots of error messages from sshd were *flying* on the console (failed to
take a photo). I could not do anything on the console. (The computer is
connected to video & keyboard via software KVM; there is no physical se=
rial<br>connection.)
After reboot of 13.1-p5, a "panic" happens all the 3-4 times I tr=
ied ...
(transcribed from the photo of the screen after booting in verbose mode)
SMP: Added CPU 1 (AP)<br>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
... What is going on here, or what had happened with 13.1 install
that the machine panics?
Booting with any of 13.0-p1[13] boot environments makes
no difference.
</pre></div></div></blockquote><div><span class=3D"gmail_default" style=3D"=
font-family:monospace">
</span><div style=3D"font-family:monospace" class=3D"gmail_default">...</di=
v><div style=3D"font-family:monospace" class=3D"gmail_default"><br></div><d=
iv style=3D"font-family:monospace" class=3D"gmail_default">After removing t=
he machine from the rack (included disconnection</div><div style=3D"font-fa=
mily:monospace" class=3D"gmail_default">of RaidMachine 24-bay disk enclosur=
e from the LSI HBA card</div><div style=3D"font-family:monospace" class=3D"=
gmail_default">installed in the machine), it booted right up (with already<=
/div><div style=3D"font-family:monospace" class=3D"gmail_default">installed=
FreeBSD 13.1-p5 on the internal disk) as if nothing</div><div style=3D"fon=
t-family:monospace" class=3D"gmail_default">had happened! There was no pani=
c or any "AP #1 (PHY #1)</div><div style=3D"font-family:monospace" cla=
ss=3D"gmail_default">failed!"-like messages.</div><div style=3D"font-f=
amily:monospace" class=3D"gmail_default"><br></div><div style=3D"font-famil=
y:monospace" class=3D"gmail_default">How? Why?</div><div style=3D"font-fami=
ly:monospace" class=3D"gmail_default"><br></div><div style=3D"font-family:m=
onospace" class=3D"gmail_default">If the machine still had panicked (after =
removal from the rack),</div><div style=3D"font-family:monospace" class=3D"=
gmail_default">then I could have tried ...</div><div style=3D"font-family:m=
onospace" class=3D"gmail_default">- updating the BIOS;</div><div style=3D"f=
ont-family:monospace" class=3D"gmail_default">- booting from 13.[01] image =
from a USB flash stick;</div><div style=3D"font-family:monospace" class=3D"=
gmail_default">- installing 13.[01] from scratch.</div><div style=3D"font-f=
amily:monospace" class=3D"gmail_default"><br></div><div style=3D"font-famil=
y:monospace" class=3D"gmail_default">Now, I do not know how much I can trus=
t the machine to</div><div style=3D"font-family:monospace" class=3D"gmail_d=
efault">not fail (panic again on a reboot).<br></div></div><div><br></div><=
div><br></div><div><div style=3D"font-family:monospace" class=3D"gmail_defa=
ult">- Anubhav</div><div style=3D"font-family:monospace" class=3D"gmail_def=
ault"></div><br></div></div></div>
--000000000000efc1c705efbb98f1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPD2KN-c_=56NvoOvHHUhr=pxKsjKrfDUkVepsZ25358T10mMg>