Re: 14.0-CURRENT panic in early boot
I've seen it on an arm64 system: KDB: stack backtrace: db_trace_self() at db_trace_self db_trace_self_wrapper() at db_trace_self_wrapper+0x30 vpanic() at vpanic+0x174 panic() at panic+0x44 do_el1h_sync() at do_el1h_sync+0x184 handle_el1h_sync() at handle_el1h_sync+0x78 --- exception, esr 0x200 vt_conswindow() at vt_conswindow+0x10 (null)() at -0x4 (null)() at 0x0001 Uptime: 3s The full log is here: http://venus.morante.net/downloads/unibia/screenshots/freebsd/R281-T91/14-CURRENT-4082b189d2c/failed-boot1.txt On 11/18/2021 12:22 AM, Dustin Marquess wrote: I just updated a machine from a build that was ~2 weeks old. The latest commit when I built it was 2e946f87055. The system boots using UEFI, if that matters. The system is panicking pretty early in the boot, however: real memory = 137438953472 (131072 MB) avail memory = 133651496960 (127460 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs FreeBSD/SMP: 2 package(s) x 8 core(s) x 2 hardware threads random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" random: unblocking device. kernel trap 12 with interrupts disabled panic: vm_fault_lookup: fault on nofault entry, addr: 0x81e1d000 cpuid = 0 time = 1 The backtrace shows: KDB: stack backtrace: #0 0x806deb5b at kdb_backtrace+0x6b #1 0x80693b44 at vpanic+0x184 #2 0x806939b3 at panic+0x43 #3 0x8091d4b3 at vm_fault+0x1423 #4 0x8091bfb0 at vm_fault_trap+0xb0 #5 0x809c0902 at trap_pfault+0x1f2 #6 0x809992b8 at calltrap+0x8 #7 0x806ebcc1 at vsscanf+0x31 #8 0x806ebc7f at sscanf+0x3f #9 0x806bd9ab at validate_uuid+0x8b #10 0x80655be0 at prison0_init+0x90 #11 0x80623aba at proc0_init+0x29a #12 0x80623689 at mi_startup+0xe9 #13 0x802e3062 at btext+0x22 Uptime: 1s Compared to a boot using the old working kernel: real memory = 137438953472 (131072 MB) avail memory = 133651505152 (127460 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs FreeBSD/SMP: 2 package(s) x 8 core(s) x 2 hardware threads random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" random: unblocking device. ioapic0 irqs 0-23 ioapic1 irqs 24-47 ioapic2 irqs 48-71 Launching APs: 1 11 28 15 18 6 29 4 16 9 24 7 3 10 27 22 14 13 12 23 25 20 26 30 17 5 2 21 19 8 31 Timecounter "TSC-low" frequency 1197250876 Hz quality 1000 Has anybody else seen this? -Dustin smime.p7s Description: S/MIME Cryptographic Signature
Re: 14.0-CURRENT panic in early boot
Just a quick update.. A kernel built from today boots just fine, so whatever the problem was, it's already fixed :). -Dustin On Thu, Nov 18, 2021 at 3:54 PM Dustin Marquess wrote: > > It was 16 days ago, so just a tad over 2 weeks :). > > Indeed, I'll start a bisect here in a few and I'll update as soon as I > know. I figured I'd ask ahead of time before I did the work :). > > Thanks! > -Dustin > > On Thu, Nov 18, 2021 at 12:29 PM Juraj Lutter wrote: > > > > > > > > On 18 Nov 2021, at 18:46, Karel Gardas wrote: > > > > > > Completely speculating, but since you don't see ioapic's are you sure this > > is just ~2 weeks old build? If not, then it may be relevant to: > > > > > > Bisecting would be a better approach. > > > > otis > > > > > > commit 1b7a2680fba589daf6f700565214919cb941ab56 > > Author: Jung-uk Kim > > Date: Thu Sep 30 16:23:21 2021 -0400 > > > >Import ACPICA 20210930 > > > >(cherry picked from commit c509b6ab0d7e5bafc5348b08653b8738bd40716e) > > > > > > > > — > > Juraj Lutter > > XMPP: juraj (at) lutter.sk > > GSM: +421907986576 > >
Re: 14.0-CURRENT panic in early boot
It was 16 days ago, so just a tad over 2 weeks :). Indeed, I'll start a bisect here in a few and I'll update as soon as I know. I figured I'd ask ahead of time before I did the work :). Thanks! -Dustin On Thu, Nov 18, 2021 at 12:29 PM Juraj Lutter wrote: > > > > On 18 Nov 2021, at 18:46, Karel Gardas wrote: > > > Completely speculating, but since you don't see ioapic's are you sure this is > just ~2 weeks old build? If not, then it may be relevant to: > > > Bisecting would be a better approach. > > otis > > > commit 1b7a2680fba589daf6f700565214919cb941ab56 > Author: Jung-uk Kim > Date: Thu Sep 30 16:23:21 2021 -0400 > >Import ACPICA 20210930 > >(cherry picked from commit c509b6ab0d7e5bafc5348b08653b8738bd40716e) > > > > — > Juraj Lutter > XMPP: juraj (at) lutter.sk > GSM: +421907986576 >
Re: 14.0-CURRENT panic in early boot
> On 18 Nov 2021, at 18:46, Karel Gardas wrote: > > > Completely speculating, but since you don't see ioapic's are you sure this is > just ~2 weeks old build? If not, then it may be relevant to: Bisecting would be a better approach. otis > > commit 1b7a2680fba589daf6f700565214919cb941ab56 > Author: Jung-uk Kim > Date: Thu Sep 30 16:23:21 2021 -0400 > >Import ACPICA 20210930 > >(cherry picked from commit c509b6ab0d7e5bafc5348b08653b8738bd40716e) > — Juraj Lutter XMPP: juraj (at) lutter.sk GSM: +421907986576
Re: 14.0-CURRENT panic in early boot
Completely speculating, but since you don't see ioapic's are you sure this is just ~2 weeks old build? If not, then it may be relevant to: commit 1b7a2680fba589daf6f700565214919cb941ab56 Author: Jung-uk Kim Date: Thu Sep 30 16:23:21 2021 -0400 Import ACPICA 20210930 (cherry picked from commit c509b6ab0d7e5bafc5348b08653b8738bd40716e) IMHO! On 11/18/21 6:22 AM, Dustin Marquess wrote: I just updated a machine from a build that was ~2 weeks old. The latest commit when I built it was 2e946f87055. The system boots using UEFI, if that matters. The system is panicking pretty early in the boot, however: real memory = 137438953472 (131072 MB) avail memory = 133651496960 (127460 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs FreeBSD/SMP: 2 package(s) x 8 core(s) x 2 hardware threads random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" random: unblocking device. kernel trap 12 with interrupts disabled panic: vm_fault_lookup: fault on nofault entry, addr: 0x81e1d000 cpuid = 0 time = 1 The backtrace shows: KDB: stack backtrace: #0 0x806deb5b at kdb_backtrace+0x6b #1 0x80693b44 at vpanic+0x184 #2 0x806939b3 at panic+0x43 #3 0x8091d4b3 at vm_fault+0x1423 #4 0x8091bfb0 at vm_fault_trap+0xb0 #5 0x809c0902 at trap_pfault+0x1f2 #6 0x809992b8 at calltrap+0x8 #7 0x806ebcc1 at vsscanf+0x31 #8 0x806ebc7f at sscanf+0x3f #9 0x806bd9ab at validate_uuid+0x8b #10 0x80655be0 at prison0_init+0x90 #11 0x80623aba at proc0_init+0x29a #12 0x80623689 at mi_startup+0xe9 #13 0x802e3062 at btext+0x22 Uptime: 1s Compared to a boot using the old working kernel: real memory = 137438953472 (131072 MB) avail memory = 133651505152 (127460 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs FreeBSD/SMP: 2 package(s) x 8 core(s) x 2 hardware threads random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" random: unblocking device. ioapic0 irqs 0-23 ioapic1 irqs 24-47 ioapic2 irqs 48-71 Launching APs: 1 11 28 15 18 6 29 4 16 9 24 7 3 10 27 22 14 13 12 23 25 20 26 30 17 5 2 21 19 8 31 Timecounter "TSC-low" frequency 1197250876 Hz quality 1000 Has anybody else seen this? -Dustin
14.0-CURRENT panic in early boot
I just updated a machine from a build that was ~2 weeks old. The latest commit when I built it was 2e946f87055. The system boots using UEFI, if that matters. The system is panicking pretty early in the boot, however: real memory = 137438953472 (131072 MB) avail memory = 133651496960 (127460 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs FreeBSD/SMP: 2 package(s) x 8 core(s) x 2 hardware threads random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" random: unblocking device. kernel trap 12 with interrupts disabled panic: vm_fault_lookup: fault on nofault entry, addr: 0x81e1d000 cpuid = 0 time = 1 The backtrace shows: KDB: stack backtrace: #0 0x806deb5b at kdb_backtrace+0x6b #1 0x80693b44 at vpanic+0x184 #2 0x806939b3 at panic+0x43 #3 0x8091d4b3 at vm_fault+0x1423 #4 0x8091bfb0 at vm_fault_trap+0xb0 #5 0x809c0902 at trap_pfault+0x1f2 #6 0x809992b8 at calltrap+0x8 #7 0x806ebcc1 at vsscanf+0x31 #8 0x806ebc7f at sscanf+0x3f #9 0x806bd9ab at validate_uuid+0x8b #10 0x80655be0 at prison0_init+0x90 #11 0x80623aba at proc0_init+0x29a #12 0x80623689 at mi_startup+0xe9 #13 0x802e3062 at btext+0x22 Uptime: 1s Compared to a boot using the old working kernel: real memory = 137438953472 (131072 MB) avail memory = 133651505152 (127460 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs FreeBSD/SMP: 2 package(s) x 8 core(s) x 2 hardware threads random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" random: unblocking device. ioapic0 irqs 0-23 ioapic1 irqs 24-47 ioapic2 irqs 48-71 Launching APs: 1 11 28 15 18 6 29 4 16 9 24 7 3 10 27 22 14 13 12 23 25 20 26 30 17 5 2 21 19 8 31 Timecounter "TSC-low" frequency 1197250876 Hz quality 1000 Has anybody else seen this? -Dustin
